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

|series    = ''Metroid''

|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}}

|genre    = First-Person Action Adventure

|modes    = Single-Player

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.

== Problems ==

=== Random Crashes ===

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

=== Scanning ===

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.

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

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.

<div style="float:left;">[[File:MP3-Pixelboxes-cropzoom.jpg|thumb|250px|Example of the pixelation]]</div>

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}}.

<div style="float:left;">[[File:MP3 NoSquish.jpg|thumb|250px|Correct emulation]]</div>

<div style="float:left;">[[File:MP3 Squish.jpg|thumb|250px|Black bar and squishing]]</div>

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

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

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

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.

<div style="float:left;">[[File:MP3-Thedot-zoom.png|thumb|175px|The dot, zoomed in 8x]]</div>

<div style="clear:both;"></div>

|gfxbackend = D3D11

|gfxbackendnotes = Needed to avoid the pixelated box problem

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

<!--Replace 'revision' with an SVN revision number (like 6789), a Dolphin release (like 3.0), or a git revision number (like 3.0-50)-->

{{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}}

{{Navigation Metroid}}