| Progress Continues
We've already had 11040 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: August/September 2019 Progress Report.
| The Dolphin Emulator Wiki needs your help!
Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin.
Metroid Prime 3: Corruption (Wii)
|Metroid Prime 3: Corruption|
|Series||Metroid, Metroid Prime|
|Release date(s)|| JP March 6, 2008|
NA August 27, 2007
EU October 26, 2007
AUS November 8, 2007
|Genre(s)||First-person action-adventure, First-person shooter, Action-adventure|
|Input methods||Wii Remote + Nunchuk|
|GameIDs||G2MEAB, RM3E01, RM3P01, RM3J01|
Metroid Prime 3: Corruption is a first-person action-adventure game developed by Retro Studios and published by Nintendo for the Wii video game console. It is the tenth game in the Metroid series, and the final entry in the Metroid Prime Trilogy. The Wii Remote and Nunchuk devices are featured in a new control scheme that took a year to develop and caused the game's release to be delayed several times.
Gameplay for Metroid Prime 3 is similar to its predecessors: players explore open ended worlds, finding story clues and power ups, solving puzzles, jumping on platforms, and fighting enemies. Unlike past games however, the game is divided into several open worlds; each world is smaller than the single open world environments of Metroid Prime or Metroid Prime 2, but the combined size is greater. As with Metroid Prime 2, exploring the worlds is not aimless: players explore the world freely, but there are specific tasks meant to be accomplished on each world which are told to you beforehand. The game also includes hypermode, a phazon overload system that allows players to exchange health for massive damage. The biggest change is the controls. Metroid Prime 3 uses a new control system using the Wii Remote and Nunchuk, allowing free aiming and movement similar to mouse and keyboard controls.
Using savestates in MP3 will crash Dolphin. Use the in-game saving to avoid any problems. Seems to have been fixed in the recent builds (4.0-5615 and onward).
Constant Wiimote 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.
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.
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 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.
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.
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.
Blue Startup Video
Only configuration options for the best compatibility where they deviate from defaults are listed.
|Disabled||Causes constant wiimote disconnects|
The graph below charts the compatibility with Metroid Prime 3: Corruption since Dolphin'srelease, listing revisions only where a compatibility change occurred.
This title has been tested on the environments listed below:
|Windows 7 x64||Intel Core 2 Duo E7300 @ 2.6GHz||nVidia GeForce GTX 275||Intro slow, but in game full speed.|
|Windows 7 x64||Intel Core 2 Quad Q6600||ATI Radeon HD 5770||20/40 frames|
|Windows 7 x64||Intel Core i7-2600K @ 3.4GHz||AMD Radeon HD 6950||Works great. Real Wiimote errors. Have to use emulated Wiimote.||Robodt7|
|Windows 7 x64||Intel Core i5-2500K @ 4.1GHz||AMD Radeon HD 6850||Runs flawlessly. 60fps all the time. Still has Wiimote control lag issues. Red blooming from light sources now fixed.||MegaJump|
|Windows 7 x64||Intel Core i5-2500K @ 3.3GHz||nVidia GeForce GTX 560 Ti||Struggle to reach 60fps. Enabling any kind of anti-aliasing has a serious hit on performance 20-40 frames on 4x internal res.||boeoz|
|Windows 8.1 x64||Intel Core i5-3570k||nVidia GeForce GTX 660 Ti||Game runs fine but slows down a lot in some places. Sometimes only the sound gets a little bit laggy but the graphics are okay, sometimes both are laggy. Map almost always is laggy. Reducing Internal Resolution helps, but not much. HLE seems a little bit better, though it suddenly stops in some cutscenes.||Thales|
|Windows 8.1 x64||Intel Core i5-3570k||nVidia GeForce GTX 660 Ti||Running just fine! Great improvement from last test. No major slowdowns and no visible annonying glitches, at least with my DSP & graphics configuration.||Thales|