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

From Dolphin Emulator Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 49: Line 49:


=== Bloom Offset ===
=== 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.
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}}.


<div style="float:left;">[[File:MP3 Bloom1.png|thumb|175px|Example of the bloom offset]]</div>
<div style="float:left;">[[File:MP3 Bloom1.png|thumb|175px|Example of the bloom offset]]</div>

Revision as of 04:30, 15 August 2012

Metroid Prime 3: Corruption
Metroid Prime 3: Corruption
Developer(s) Retro Studios
Publisher(s) Nintendo
Series Metroid
Platform(s) Wii
Release date(s) JP March 6, 2008
NA August 27, 2007
AUS November 8, 2007
Genre(s) First Person Action Adventure
Mode(s) Single-Player
Input methods Wii Remote + Nunchuk
Compatibility 5Stars5.pngEdit rating: Metroid Prime 3: Corruption (Wii)
Perfect
GameIDs
See also...

Trilogy Version
Search Dolphin Forums
Open Issues
Search Google
Search Wikipedia

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 (excluding two spin-off titles). It was released in North America and Europe in 2007, and in Japan the following year. 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.

Metroid Prime 3 was also included in the Metroid Prime: Trilogy pack which includes updated versions of its prequels: Metroid Prime and Metroid Prime 2: Echoes.

Problems

Random Crashes

Prime 3 has a tenancy to crash randomly. There is no solution to this problem at this time, but restarting should allow you to get past the crash point. Save often.

Savestates

Using savestates in MP3 will crash Dolphin. Use the in-game saving to avoid any problems.

Scanning

The scan visor will not work with EFB to Texture. Use EFB to RAM to make it functional.

Wiimote Lag

The game may experience a large amount of Wii Remote lag. Use "Alternate Wiimote Timings" in the game settings to correct it.

Audio Problems, Stalls

The game will have numerous audio problems with DSP HLE, and it may stall out during the "Input Identity Code" sequence at the start of the game. Even DSP LLE cannot correct all of these problems, but it is much more better overall.

Dynamic Loading Issues

Metroid Prime 3, like all Metroid Prime games, uses dynamic loading to load areas seamlessly. On the Wii, it creates the appearance of no loading whatsoever. However Dolphin has some problems with this feature, and "studders" as it loads new areas. This is most apparent when moving through areas quickly, forcing it to load constantly. There is currently no fix for this problem, but, while it may be very annoying, it is not game breaking. Use "Speed Up Disc Transfer Rate" in the game settings to alleviate the problem somewhat. It does not correct it completely, but it helps.

EFB to Ram 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.

File:MP3-Pixelboxes-cropzoom.jpg
Example of the pixelation

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.

Correct emulation
Black bar and squishing

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.

Example of the bloom offset
Another example of the offset

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.

The dot, zoomed in 8x

Configuration

Only configuration options for the best compatibility where they deviate from defaults are listed.

Graphics

Config Setting Notes
Video Backend D3D11 Needed to avoid the pixelated box problem

Audio

Config Setting Notes
DSP Emulator Engine LLE Avoid sound problems and stalls

Game Properties

Config Setting Notes
Speed up Disc Transfer Rate On Improves dynamic loading

Version Compatibility

The graph below charts the compatibility with Metroid Prime 3: Corruption since Dolphin's 2.0 release, listing revisions only where a compatibility change occurred.

Δ
5.0-21536 (current)
Δ
Δ
Δ
Δ
Δ
2.0 (r5384)
Compatibility can be assumed to align with the indicated revisions. However, compatibility may extend to prior revisions or compatibility gaps may exist within ranges indicated as compatible due to limited testing. Please update as appropriate.

Testing

This title has been tested on the environments listed below:

Test Entries
Revision OS CPU GPU Result Tester
r5442 Windows 7 x64 Intel Core 2 Duo E7300 @ 2.6GHz nVidia GeForce GTX 275 Intro slow, but in game full speed.
r7111 Windows 7 x64 Intel Core 2 Quad Q6600 ATI Radeon HD 5770 20/40 frames
r7478 Windows 7 x64 Intel Core i7 2600K @ 3.4GHz AMD Radeon HD 6950 Works great. Real Wiimote errors. Have to use emulated Wiimote. Robodt7
r7670 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
r7670 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

Gameplay Videos