Metroid Prime 3: Corruption (Metroid Prime: Trilogy)

Metroid Prime: Trilogy is an action-adventure video game compilation developed by Retro Studios and published by Nintendo for the Wii video game console. It features Metroid Prime, Metroid Prime 2: Echoes, and Metroid Prime 3: Corruption on a single dual-layer disc.

Metroid Prime 3 in Trilogy is more or less a direct copy of the original Wii release. However, it uses the Metroid Prime Trilogy menus, achievements, saving system, and unlockable soundtracks; and it has extended versions of the Bryyo music tracks to make them less repetitive.

Game Pages
This page should be used for specific issues with the Metroid Prime sub-game of Metroid Prime: Trilogy. For other Metroid Prime: Trilogy games or launcher information, please see the following pages.



Constant Wii Remote Disconnects
Since, 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.

Shader Generation Stuttering and the Black Bar
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 Metroid Prime 3, 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 is the only solution currently available, and both result in a significant performance hit on one of Dolphin's most demanding games. See.
 * PAL users can disable "PAL60 Mode (EuRGB60)" in the Wii settings to prevent the black bar from appearing. The stuttering during shader generation will remain, however.

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. The only solution is to disable "Scaled EFB Copy", but this has some issues of its own. See.

Visors
Visors will only work if EFB Copies to Texture Only is disabled. Though EFB Copies to Texture Only is forced off by the GameINI, visor corruption may still occur if the graphics configuration window is opened during gameplay. Disable EFB Copies to Texture Only in the Dolphin GUI to avoid any problems.

Dot
When playing above 1x Native internal resolution, there is a dot in the center of the screen. It's small and easy to ignore, but it's always there. There is no fix for this problem.

Savestates
Using savestates in MP3 will crash Dolphin. Use the in-game saving to avoid any problems. Seems to be fixed in recent builds ( and onward).

Pixelation Glitches
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). To avoid this problem, use the D3D graphics backend. Fixed by, and detailed in the February Progress Report

Refraction Slowdown
Refraction effects, such as raindrops on Samus' visor and the heat effect after firing her weapon for an extended period, cause slowdown on all backends. OpenGL is affected worse, though D3D is affected as well. It also has slowdowns when several grapple points (yellow pulsing) are present on screen at once. Even the strongest computers are affected by this issue, and there is no solution at this time. Fixed by.