5,502
edits
Metroid Prime 3: Corruption (Wii): Difference between revisions
Black Bar update, added wiimote disconnects
(New AX HLE 2.0 merger. Tested.) |
(Black Bar update, added wiimote disconnects) |
||
| Line 28: | Line 28: | ||
=== Micro-stuttering === | === Micro-stuttering === | ||
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. | ||
=== Constant Wiimote Disconnects === | |||
Since {{revision|3.5-471}}, Prime 3 will think that the wiimote is constantly disconnecting. Pressing Alt-F5 will restore it, but it will disconnect again seconds later. Disable "Enable Speaker Data" to solve this problem. | |||
=== Pixelation Glitches === | === Pixelation Glitches === | ||
| Line 34: | Line 37: | ||
=== Black Bar === | === Black Bar === | ||
At seemingly random points throughout the game, 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. 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|MP3 NoSquish.jpg|Correct emulation}} | {{image|MP3 NoSquish.jpg|Correct emulation}} | ||
| Line 66: | Line 69: | ||
<!--A full list of options is available at Template:Config/doc--> | <!--A full list of options is available at Template:Config/doc--> | ||
{{Config | {{Config | ||
|enablespeakerdata = Disabled | |||
|enablespeakerdatanotes = Causes constant wiimote disconnects | |||
}} | }} | ||