Dolphin Emulator Wiki

Metroid Prime (Metroid Prime: Trilogy): Difference between revisions

Page Discussion

Metroid Prime (Metroid Prime: Trilogy) (view source)

Revision as of 18:11, 10 April 2013

707 bytes added ,  10 April 2013
no edit summary
(New AX HLE 2.0 merger. Tested.)
No edit summary
Line 25: Line 25:
Performance in general seems reduced compared to the game's GameCube counterpart. This may be related to the higher resolution textures and various new screen effects added for the Trilogy versions.
Performance in general seems reduced compared to the game's GameCube counterpart. This may be related to the higher resolution textures and various new screen effects added for the Trilogy versions.


=== Micro-stuttering ===
=== Black Bar and Severe Stutters ===
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.
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 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}}.
 
=== Black Bar ===
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.
*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|MP1Tri NoSquish.jpg|Correct emulation}}
{{image|MP1Tri NoSquish.jpg|Correct emulation}}
{{image|MP1Tri Squish.jpg|Black bar and squishing|br}}
{{image|MP1Tri Squish.jpg|Black bar and squishing|br}}
=== Constant Wiimote Disconnects ===
Since {{revision|3.5-471}}, the game 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.
=== Audio Issues ===
The New-AX-HLE 2.0 merger in {{revision|3.5-1154}} causes SEVERE audio problems with DSP HLE with DSP on Dedicated Thread disabled. Run DSP HLE with DSP on Dedicated Thread on, or use [[DSP LLE]]. See {{issue|6237}}.
=== Micro-stuttering ===
All of the Prime games suffer from micro-stuttering: 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. 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.


=== Bloom Offset ===
=== Bloom Offset ===
Like Prime 3 and all the Trilogy games, Prime 1 Trilogy has bloom offset problems. Fortunately, it is not very noticeable with this game. The only solution is to disable Scaled EFB copies, which creates issues of its own. See {{issue|5573}}.
Like Prime 3 and all the Trilogy games, Prime 1 Trilogy has bloom offset problems. Fortunately, it is not very noticeable with this game. The only solution is to disable Scaled EFB copies, which creates issues of its own. See {{issue|5573}}.
{{image|MP1Tri-Bloom.png|Example of the bloom offset|br}}
{{image|MP1Tri-Bloom.png|Example of the bloom offset|br|width=200}}


=== Refraction Slowdown ===
=== Refraction Slowdown ===
Line 48: Line 53:
=== Visors ===
=== Visors ===
Visors will only work if EFB to Ram is enabled. However, EFB to Ram is set as default within the game INI, preventing the user from using anything but EFB to Ram for this game.
Visors will only work if EFB to Ram is enabled. However, EFB to Ram is set as default within the game INI, preventing the user from using anything but EFB to Ram for this game.
=== <s>Audio Issues</s> ===
Several sounds don´t play appropriately, and sometimes music stops playing. Use [[DSP LLE]] to correct it. See {{issue|5563}}. Fixed by the merger of New-AX-HLE 2.0 in {{revision|3.5-1154}}.


=== <s>Wiimote Lag</s> ===
=== <s>Wiimote Lag</s> ===
Line 58: Line 60:
<!--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
}}
}}


Retrieved from "https://wiki.dolphin-emu.org/index.php?title=Special:MobileDiff/61739"