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

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

Revision as of 00:26, 9 November 2012

379 bytes added , 9 November 2012

Copied over edits from Metroid Prime 3 Corruption (Wii)

MayImilae

Bureaucrats, Administrators

5,502

edits

@@ Line 29: / Line 29: @@
 Using savestates in MP3 will crash Dolphin. Use the in-game saving to avoid any problems.
-=== Scanning ===
+=== Wiimote Lag ===
-The scan visor will not work with EFB to Texture. Use EFB to RAM to make it functional.
+The game may experience a large amount of Wii Remote lag. Use "Alternate Wiimote Timings" in the game settings to correct it. Dolphin 3.0 does not have this setting, making control of this game very difficult for that version.
-=== Wiimote Lag ===
+=== Visors ===
-The game may experience a large amount of Wii Remote lag. Use "Alternate Wiimote Timings" in the game settings to correct it.
+Visors will only work if EFB to Ram is enabled. Unlike the original Prime releases, Trilogy does not have EFB to Ram enabled by default in the GameINI, and must be set manually.
 === Audio Problems, Stalls ===
-The game will have numerous audio problems with DSP HLE, such as sound effects issues and a few seconds of music randomly looping forever. and it may stall out during the "Input Identity Code" sequence at the start of the game. [[DSP LLE]] makes it a lot better, but LLE creates stuttering problems. See {{issue|5563}}.
+The game will have numerous audio problems with DSP HLE, such as sound effects issues and a few seconds of music randomly looping forever. And it may stall out during the "Input Identity Code" sequence at the start of the game. [[DSP LLE]] makes it a lot better, but LLE creates stuttering problems in some revisions. See {{issue|5563}}.
-=== EFB to Ram Pixelation Glitches ===
+=== Pixelation Glitches ===
-With EFB to Ram active, a large pixelated block may appear in the upper left area of the frame. It usually only appears during camera movement, but it may also appear after using the command visor. To avoid this problem, use the D3D11 graphics backend.
+A large pixelated block may appear in the upper left area of the frame. It may only appear during movement (newer revisions) or be stuck there permanently (older revisions), and it may appear after using the command visor. To avoid this problem, use the D3D11 graphics backend.
 <div style="float:left;">[[File:MP3-Pixelboxes-cropzoom.jpg|thumb|250px|Example of the pixelation]]</div>
@@ Line 45: / Line 45: @@
 === 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. See {{issue|5574}}.
+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. See {{issue|5574}}. Old versions of Dolphin, such as 3.0-135, do not have this issue on all backends.
 <div style="float:left;">[[File:MP3 NoSquish.jpg|thumb|250px|Correct emulation]]</div>
@@ Line 52: / Line 52: @@
 === Bloom Offset ===
-Prime 3 has noticeable bloom offset problems. It will have several copies of the bloom spread out from the source, and can be very distracting. There is no known solution to this issue. See {{issue|5573}}.
+Prime 3 has noticeable bloom offset problems. It will have several copies of the bloom spread out from the source, and can be very distracting. The only solution is to disable "Scaled EFB Copy", but this has some issues of its own from the low resolution bloom. See {{issue|5573}}.
 <div style="float:left;">[[File:MP3 Bloom1.png|thumb|175px|Example of the bloom offset]]</div>