Project

General

Profile

Actions

Emulator Issues #2327

closed

Super Mario Galaxy: Pressing wiimote D-upwards to set camera to first person makes the screen go black.

Added by PianoGamer almost 15 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

What steps will reproduce the problem?
1.Start Super Mario Galaxy
2.In game, press the D-pad up button

What is the expected output? What do you see instead?
View should be set to first person, instead the whole screen goes black
untill you quit the game, but from sound you hear it's working normally

What version of the product are you using? On what operating system?
r5062 x64
Specs: Core2Duo E8400 3,0 Ghz;
4Gb RAM; NVIDIA GeForce GTX 260;
Win7 64-Bit

Please provide any additional information below.
It also happens in certain other sequences with a camera view change (like
when entering the piranha boss battle in Good Egg Galaxy). It worked some
revisions back (last I tested a while ago)

Actions #2

Updated by DimitriPilot3 almost 15 years ago

Tested in R5141:

This problem occurs in the D3D plugin when SSAA is enabled in the plugin's settings.
The current SSAA implementation doesn't seem to like the "motion blur" effects in that
game...

If the anti-aliasing setting is set to None, no error occurs and the screen doesn't
black out (or it is no longer black if the error occured before). If this setting is
enabled, the "Create Color Texture" and "Depth Color Texture" errors from
FBManager::Create pop up and the screen blacks out until SSAA is disabled.

IIRC, the first time I got these errors, I even got "No EFB color" kind of errors
that occur several times per frame... So there is a problem with EFB and SSAA.

Actions #3

Updated by romaniox over 14 years ago

I can confirm this and it does happen also with both AFx16 and any SSAA OFF. I have
gtx260. Though I use r5186 32bit. OpenGL no problem but slow. Its DirectX plugin
problem and not just SSAA related.

Actions #4

Updated by wespipes69 over 14 years ago

Happens to me with no AA using the D3D plugin. Confirmed.

Actions #5

Updated by Xtreme2damax over 14 years ago

I'm just wondering how this got marked as a game issue, when it in fact seems to be
an emulator bug/issue? I can confirm this issue as well, although it doesn't happen a
whole let throughout the game.

Actions #6

Updated by NeoBrainX over 14 years ago

  • Status changed from New to Won't fix

The causation of this issue is that the game tries to set a very wide viewport when going to 1st person perspective. When using multisampling, the viewport will even get bigger. A changed viewport means that the EFB textures need to be recreated, and thus Dolphin tries to create a SOMEWHAT large EFB texture (more than 16384 in many cases) and of course fails to do so (Direct3D has a max texture size, whereas OpenGL apparently has not).
Sometimes we only get a blackscreen, sometimes the emulator even crashes. I introduced a workaround for this in r5870, but it might/will introduce glitches in the few frames/seconds after the moment where a blackscreen would've occured before.

Anyway, there's nothing we can do about this, since it's a limitation of Direct3D.

Actions #7

Updated by JMC4789 over 11 years ago

  • Status changed from Won't fix to Fixed

This no longer happens in D3D back-ends.

Actions

Also available in: Atom PDF