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

Metroid Prime 2: Echoes (GC) (view source)

Revision as of 08:41, 17 August 2015

205 bytes removed , 17 August 2015

Removing until someone confirms that the Dolphin widescreen hack is misbehaving on this game and these codes are needed. More info: https://wiki.dolphin-emu.org/index.php?title=User_talk:UmbraWitchJeanne#Animal_Crossing_16:9_AR_code

Karasuhebi

90

edits

@@ Line 19: / Line 19: @@
 == Patches ==
-=== 16:9 Aspect Ratio (Widescreen) AR Codes ===
-===== PAL[http://www.gc-forever.com/forums/viewtopic.php?f=38&t=1998] =====
-<pre>16:9 Aspect Ratio (Widescreen) [Ralf]
-CB6T-R47A-UDEBV
-NUNH-6Q3A-K3V6X</pre>
 === 60Hz AR Codes ===
 ===== PAL[http://www.gc-forever.com/forums/viewtopic.php?f=38&t=1998] =====
@@ Line 34: / Line 28: @@
 === Shader Generation Stuttering and the Black Bar ===
-This game suffers from severe stuttering during shader generation. Because of the differences between how the Gamecube works compared to personal computers, whenever something uses the Gamecube'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 this game, 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 stutter and desync if a new effect or region is loaded.
+This game suffers from severe stuttering during shader generation. Because of the differences between how the GameCube works compared to personal computers, whenever something uses the GameCube'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 this game, 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 stutter and desync if a new effect or region is loaded.
 There is no solution at this time. Playing with Dual Core disabled or using Sync GPU Thread are the only solutions currently available, and both result in a significant performance hit. See {{issue|4336}} and {{issue|5185}}.
@@ Line 81: / Line 75: @@
 {{VideoGallery
 |vid1=eeBaMXB7O0M|cap1=Dolphin Emulator 4.0 - Metroid Prime 2: Echoes (1080p HD) - Nintendo GameCube
-|vid2=Myt5wMEyIF4|cap2=Metroid Prime 2 on Dolphin 1943 (Emulator) - High Quality (Normaly running on 45-60FPS!!!)
+|vid2=Myt5wMEyIF4|cap2=Metroid Prime 2 on Dolphin 1943 (Emulator) - High Quality (Normally running on 45-60FPS!!!)
 }}<div style="clear:left;"></div>