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

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

Revision as of 05:04, 26 November 2015

1,121 bytes removed , 26 November 2015

→‎Problems

Kolano

Bureaucrats, Administrators

79,225

edits

@@ Line 36: / Line 36: @@
 <!-- Copied from [[Metroid Prime: Trilogy#Constant Wii Remote Disconnects]] -->
 Since {{revision|3.5-471}}, when using the MS Bluetooth Stack (the default Bluetooth stack on Windows) the game will think that the Wii Remote is constantly disconnecting. Pressing a button on the Wii Remote will restore it, but it will disconnect again seconds later. Disable "Enable Speaker Data" to solve this problem, or avoid the MS Bluetooth stack by using the DolphinBar or the Toshiba Stack (for instruction of which is available at [[Wii Remote Plus (RVL-CNT-01-TR) Connection Guide#Windows]]).
-=== Shader Compilation Stuttering ===
-The ''Metroid Prime'' games are some of the most susceptible titles to shader compilation stuttering, thanks to a combination of very complex effects and dynamic loading. The GC and Wii have no concept of shaders - everything runs directly "on the metal" without any APIs. Modern desktop and phone systems do not work in this way, requiring the use of shaders as an intermediary so your system's GPU can perform the tasks that the GC and Wii GPU performed. But shaders have to be created, and since GC/Wii games are not designed to create shaders ahead of time as a PC game would, when a new effect appears Dolphin has to delay the CPU thread while the GPU thread performs the compilation; a pause that does not exist on the consoles. For most games shader generation takes only a few milliseconds, but for the ''Metroid Prime'' series and a few other demanding titles, the shaders that they generate are so large that they can result in noticeable stuttering.
-Eventually stuttering will reduce as a shader cache is built up, but there is no solution to this problem at this time.
 === Bloom Offset ===