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

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

Revision as of 12:40, 21 September 2014

408 bytes added , 21 September 2014

Porting relevant changes from Metroid Prime 3: Corruption (Wii)

MayImilae

Bureaucrats, Administrators

5,502

edits

@@ Line 28: / Line 28: @@
 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.
-=== Black Bar and Severe Stutters ===
+=== Shader Generation Stuttering and the Black Bar ===
-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}}.
+This game suffers from severe stuttering during shader generation. Because of the differences between how the Wii works compared to personal computers, whenever something uses the Wii's GPU, Dolphin must generate a shader to emulate it on a PC GPU. Shader generation causes a slight emulation delay while it's being created, so Dolphin caches these shaders in its shadercache folder to help keep things smooth. Most games don't care about this and play fine, but with all of the games in ''Metroid Prime Trilogy'', the shaders are so massive that they cause a significant delay, which creates a hard stutter and desyncs the GPU and CPU threads. The game freaks out over this desync, creating a black bar at the bottom of the screen, which takes up 15% of the screen space and "squishes" the game in the remaining space. The black bar will remain there from then on whether stuttering continues or ceases. Going into new areas or showing new effects will cause the stutter and black bar, 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.
-*PAL users can disable "EuRGB60 Mode (PAL60)" in the Wii settings to prevent this issue.
+There is no solution at this time. Playing with Dual Core disabled or using Sync GPU Thread is the only solution currently available, and both result in a significant performance hit on one of Dolphin's most demanding games. See {{issue|5185}}.
+*PAL users can disable "EuRGB60 Mode (PAL60)" in the Wii settings to prevent the black bar from appearing. The stuttering during shader generation will remain, however.
 {{image|MP1Tri NoSquish.jpg|Correct emulation}}
 {{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.
+Since {{revision|3.5-471}}, when using the MS Bluetooth Stack (the default bluetooth stack on Windows) Prime 3 will think that the wiimote is constantly disconnecting. Pressing Alt-F5 will restore it, but it will disconnect again seconds later. Windows users can disable "Enable Speaker Data" to solve this problem, or move to either the Toshiba Stack or the DolphinBar.
-=== 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 ===
@@ Line 50: / Line 49: @@
 === Visors ===
-Visors will only work if EFB to Ram is enabled. Though EFB to Ram is forced by the GameINI, visor corruption may still occur. Turn on EFB to Ram in the Dolphin GUI to avoid any problems.
+Visors will only work if EFB to Ram is enabled. Though EFB to Ram is forced by the GameINI, visor corruption may still occur if you open the graphics configuration window during gameplay. Turn on EFB to Ram in the Dolphin GUI to avoid any problems.
 === Dot ===