Metroid Prime 2: Echoes (GC): Difference between revisions

Jump to navigation Jump to search
Copied over the black bar changes
(New AX HLE 2.0 merger. Tested.)
(Copied over the black bar changes)
Line 23: Line 23:
All of the Prime games suffer from micro-stuttering: screen redraws and small stops in the video that can become very annoying. It occurs in all graphics backends, but the OpenGL backend has consistently been the most resistant to the problem. DSP HLE and DSP LLE are both affected, though DSP LLE appears to make it worse in some revisions. Its severity varies depending on the revision and settings used, so if you want to play the game you should try a wide variety of combinations. Micro-stuttering can trigger the Black Bar glitch.
All of the Prime games suffer from micro-stuttering: screen redraws and small stops in the video that can become very annoying. It occurs in all graphics backends, but the OpenGL backend has consistently been the most resistant to the problem. DSP HLE and DSP LLE are both affected, though DSP LLE appears to make it worse in some revisions. Its severity varies depending on the revision and settings used, so if you want to play the game you should try a wide variety of combinations. Micro-stuttering can trigger the Black Bar glitch.


=== Black Bar ===
=== Black Bar and Severe Stutters ===
Whenever Dolphin has trouble with the game and flickers, from a loading hiccup to taking a screenshot, a black bar will appear on the bottom of the screen, taking up 15% of the screen space and "squishing" the game in the remaining space. This occurs in all graphics backends, and there is no known solution, but OpenGL is the most resistant. See {{issue|5185}}. Old versions of Dolphin, such as 3.0-135, do not have this issue on all backends.
At seemingly random points throughout the game, the game will freeze for an instant, flashing to black and "redrawing". When it comes back, a black bar will be at the bottom of the screen, taking up 15% of the screen space and "squishing" the game in the remaining space. From thorough testing, this apparently occurs whenever the emulator stops the GPU thread for a split-second, causing the GPU and CPU threads to desync. Most games don't care about this, but Prime 3 freaks out and creates this error. Creating a new shadercache, from first run of the game or from going into a new area, will immediately cause the desync, as well as going in and out of fullscreen and even taking a screenshot. Building up a shadercache of an area helps, but it will still desync if a new effect or region is loaded. Playing with Dual Core disabled or using Sync GPU Thread is the only solution at this time. See {{issue|5185}}.
*PAL users can disable "EuRGB60 Mode (PAL60)" in the Wii settings to prevent this issue.
*PAL users can disable "EuRGB60 Mode (PAL60)" in the Wii settings to prevent this issue.
{{image|MP2GC NoSquish.jpg|NTSC Correct emulation}}
{{image|MP2GC NoSquish.jpg|NTSC Correct emulation}}

Navigation menu