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

|series    = ''Metroid'', ''Metroid Prime''

|released  = '''Original release'''<br/>{{Vgrelease|NA=August 27, 2007|EU=October 26, 2007|AUS=November 8, 2007}}{{Vgrelease|JP=March 6, 2008}}'''''Metroid Prime: Trilogy'''''<br/>{{Vgrelease|NA=August 24, 2009|EU=September 4, 2009|AUS=October 15, 2009}}

|forumlink = http://forums.dolphin-emu.org/Thread-wii-metroid-prime-trilogy--26043

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.

=== Random Crashes ===

Prime 3 has a tendency to crash randomly, its severity depending on the revision used. There is no known solution to this problem at this time, but restarting should allow you to get past the crash point. Save often.

 

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

Since {{revision|3.5-471}}, Prime 3 will think that the wiimote is constantly disconnecting. Pressing Alt-F5 will restore it, but it will disconnect again seconds later. Disable "Enable Speaker Data" to solve this problem.

{{image|MP3 Squish.jpg|Black bar and squishing|br}}

 

All of the Prime games suffer from micro-stuttering: small stops in the video that can become very annoying. It occurs in all graphics backends, but the OpenGL backend has consistently been the most resistant to the problem. DSP HLE and DSP LLE are both affected, though DSP LLE appears to make it worse in some revisions. Its severity varies depending on the revision and settings used, so if you want to play the game you should try a wide variety of combinations.

 

{{image|MP3-Pixelboxes-cropzoom.jpg|Example of the pixelation, top half is blurred|br}}

=== 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 {{issue|5573}}.

=== Visors ===

Visors will only work if EFB to Ram is enabled. Though EFB to Ram is forced by the GameINI, visor corruption may still occur. 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.

|enablespeakerdata      = Disabled

|enablespeakerdatanotes = Causes constant wiimote disconnects

<!--Use this template for compatibility entries: {{VersionCompatibilityVersion|revision|****}}-->

{{VersionCompatibilityVersion|3.0|***}}

{{testing/entry|revision=3.0-735|OS=Windows 7 x64|CPU=Intel Core i5-3570K @ 4.7GHz|GPU=nVidia GeForce GTX 275|result=Used Dol swapping. MP3 with LLE and EFB to Ram are difficult even for my system; it usually is at 60 FPS but drops are common. I experienced all the problems listed above.|tester=MaJoR}}

{{testing/entry|revision=3.5-392|OS=Windows 7 x64|CPU=Intel Core i7-2600k|GPU=nVidia GeForce GTX 560|result="Accurate VBeam emulation" enabled in properties file. Direct3D11 backend, EFB to texture, 2.5x resolution, DSP HLE and XAudio2. Tested in first Norion section - almost perfect emulation, slight slowdown when using Scan Visor, and the odd tiny audio blip. Dot glitch present. (PAL version.)|tester=-}}

{{Navigation Metroid}}