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

From Dolphin Emulator Wiki
Jump to navigation Jump to search
mNo edit summary
(23 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{Infobox VG
{{Infobox VG
|title        = Metroid Prime 3: Corruption
|image     = [[File:MetroidPrime3Corruption.jpg|300px]]
|image         = [[File:MetroidPrime3Corruption.jpg|300px|Metroid Prime 3: Corruption]]
|developer = Retro Studios
|developer     = Retro Studios
|publisher = Nintendo
|publisher     = Nintendo
|series   = Metroid, Metroid Prime
|series       = ''Metroid'', ''Metroid Prime''
|released = {{Vgrelease|NA=August 27, 2007|EU=October 26, 2007|AUS=November 8, 2007|JP|March 6, 2008}}
|released     = {{Vgrelease|NA=August 27, 2007|EU=October 26, 2007|AUS=November 8, 2007|JP=March 6, 2008}}
|genre     = First-person action-adventure, First-person shooter, Action-adventure
|genre         = First-person action-adventure, First-person shooter, Action-adventure
|modes     = Single-player
|modes         = Single-player
|input     = Wii Remote + Nunchuk
|input         = Wii Remote + Nunchuk
|forumlink = http://forums.dolphin-emu.org/Thread-wii-metroid-prime-3-corruption--26000
|forumlink     = http://forums.dolphin-emu.org/Thread-wii-metroid-prime-3-corruption--26000
}}
}}


Line 19: Line 18:


== Emulation Information ==
== Emulation Information ==
{{Problems/ShaderCompStuttering}}
== Problems ==
=== Constant Wii Remote Disconnects ===
=== Constant Wii Remote Disconnects ===
Since {{revision|3.5-471}}, when using the MS Bluetooth Stack (the default bluetooth stack on Windows) Prime 3 will think that the Wii Remote is constantly disconnecting. Pressing a button on the Wii Remote 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.
Since {{revision|3.5-471}}, when using the MS Bluetooth Stack (the default bluetooth stack on Windows) Prime 3 will think that the Wii Remote is constantly disconnecting. Pressing a button on the Wii Remote 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.


=== Bloom Offset ===
{{Problems/Shader Compilation Stuttering}}
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}}.
{{image|MP3 Bloom1.png|Example of the bloom offset}}
{{image|MP3 Bloom2.png|Another example of the offset|br}}


=== Visors ===
== Problems ==
The Scan visor will only work if '''Store EFB Copies to Texture Only''' is disabled. Though '''Store EFB Copies to Texture Only''' is forced off by the GameINI, visor issues may still occur if the graphics configuration window is opened during gameplay. Disable '''Store EFB Copies to Texture Only''' in the Dolphin GUI to avoid any problems.
{{Problems|{{#vardefineecho:problems|
 
=== <s>Visors</s> ===
=== Dot ===
The Scan visor will only work if '''Store EFB Copies to Texture Only''' is disabled. Though '''Store EFB Copies to Texture Only''' is forced off by the GameINI, visor issues may still occur if the graphics configuration window is opened during gameplay. Disable '''Store EFB Copies to Texture Only''' in the Dolphin GUI to avoid any problems. Corrected with revised default setting handling.
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.
{{image|MP3-Thedot-zoom.png|The dot, zoomed in 8x|br}}
 
=== The Black Bar ===
During Shader Compilation, stuttering can become so severe that it desyncs the GPU and CPU threads in Dual Core mode. 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.


After {{revision|4.0-7517}}, enabling Virtual XFB or Real XFB will fix and/or prevent the problem. If XFB is disabled the problem may still occur. Details can be found in the [https://dolphin-emu.org/blog/2015/10/01/dolphin-progress-report-september-2015/#40-7517-derive-field-timings-from-video-interface-registers-by-booto September Progress Report].
=== <s>The Black Bar</s> ===
If the CPU and GPU threads of Dolphin desync too much during lag, a black bar may show up at the bottom of the screen.  It 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. Because shader compilation stuttering is the main cause for these desyncs on a powerful computer, enabling Hybrid Mode Ubershaders or Exclusive Mode Ubershaders should help with preventing this issue.  Enabling Single Core will remove any risk of this issue occurring. Fixed with Hybrid XFB in {{revision|5.0-5874}}.


{{image|MP3 NoSquish.jpg|Correct emulation}}
{{image|MP3 NoSquish.jpg|Correct emulation}}
{{image|MP3 Squish.jpg|Black bar with the squished image|br}}
{{image|MP3 Squish.jpg|Black bar with the squished image|br}}


=== {{s}}Savestates{{/s}} ===
}}}}
Using save states in MP3 will crash Dolphin. Use the in-game saving to avoid any problems. Seems to have been fixed in the recent builds ({{revision|4.0-5615}} and onward).


=== {{s}}Pixelation Glitches{{/s}} ===
== Enhancements ==
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 {{revision|4.0-5523}}, and detailed in the [https://dolphin-emu.org/blog/2015/03/01/dolphin-progress-report-february-2015/#40-5523-fix-hashing-for-the-last-byte-by-mimimi February Progress Report]
=== Bloom Offset in IR>1 ===
{{image|MP3-Pixelboxes-cropzoom.jpg|Example of the pixelation, top half is blurred|br}}
Prime 3 has noticeable bloom offset problems when playing above 1x Native internal resolution. 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}}.
{{image|MP3 Bloom1.png|Example of the bloom offset}}
{{image|MP3 Bloom2.png|Another example of the offset|br}}


=== {{s}}Refraction Slowdown{{/s}} ===
=== Dot in IR>1 ===
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 {{revision|4.0-5124}}.
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.
 
{{image|MP3-Thedot-zoom.png|The dot, zoomed in 8x|br}}
=== {{s}}Blue Startup Video{{/s}} ===
Since {{revision|4.0-216}}, the opening video is... blue. It goes away as soon as a Wii Remote appears on the screen or after a period of time. It has no effect on gameplay. See {{issue|6783}}. Fixed by {{revision|4.0-3334}}.
{{image|Metroid Prime 3 Blue Opening.jpg|Example of the blue opening video|br}}


== Configuration ==
== Configuration ==
<!--A full list of options is available at Template:Config/doc-->
<!--A full list of options is available at Template:Config/doc-->
{{Config
{{Config
|xfb = Virtual
|ubershaders            = Hybrid
|xfbnotes = Needed to prevent the black bar
|ubershadersnotes      = Needed to avoid shader compilation stuttering
|efb2texonly = Off
|efb2texonlynotes = Needed to avoid visor issues
|enablespeakerdata      = Off
|enablespeakerdata      = Off
|enablespeakerdatanotes = Causes constant Wii Remote disconnects
|enablespeakerdatanotes = Causes constant Wii Remote disconnects
Line 75: Line 60:
{{VersionCompatibilityVersion|3.5-367|***|Unplayable due to framelimiter problems}}
{{VersionCompatibilityVersion|3.5-367|***|Unplayable due to framelimiter problems}}
{{VersionCompatibilityVersion|3.5-380|***|Framelimiter problems fixed}}
{{VersionCompatibilityVersion|3.5-380|***|Framelimiter problems fixed}}
{{VersionCompatibilityVersion|5.0-4869|****|Shader Compilation Stuttering resolved with Ubershaders}}
{{VersionCompatibilityClose}}
{{VersionCompatibilityClose}}


Line 85: Line 71:
{{testing/entry|revision=7670|OS=Windows 7|CPU=Intel Core i5-2500K @ 4.1GHz|GPU=AMD Radeon HD 6850|result= Runs flawlessly.  60FPS all the time.  Still has Wii Remote control lag issues.  Red blooming from light sources now fixed.|tester=MegaJump}}
{{testing/entry|revision=7670|OS=Windows 7|CPU=Intel Core i5-2500K @ 4.1GHz|GPU=AMD Radeon HD 6850|result= Runs flawlessly.  60FPS all the time.  Still has Wii Remote control lag issues.  Red blooming from light sources now fixed.|tester=MegaJump}}
{{testing/entry|revision=7670|OS=Windows 7|CPU=Intel Core i5-2500K @ 3.3GHz|GPU=NVIDIA GeForce GTX 560 Ti|result=Struggle to reach 60FPS. Enabling any kind of anti-aliasing has a serious hit on performance 20-40 frames on 4x internal res.|tester=boeoz}}
{{testing/entry|revision=7670|OS=Windows 7|CPU=Intel Core i5-2500K @ 3.3GHz|GPU=NVIDIA GeForce GTX 560 Ti|result=Struggle to reach 60FPS. Enabling any kind of anti-aliasing has a serious hit on performance 20-40 frames on 4x internal res.|tester=boeoz}}
{{testing/entry|revision=4.0.2-2879|OS=Windows 8.1|CPU=Intel Core i5-3570K|GPU=NVIDIA GeForce GTX 660 Ti|result=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.|tester=Thales}}
{{testing/entry|revision=4.0-2879|OS=Windows 8.1|CPU=Intel Core i5-3570K|GPU=NVIDIA GeForce GTX 660 Ti|result=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.|tester=Thales}}
{{testing/entry|revision=4.0-4167|OS=Windows 8.1|CPU=Intel Core i5-3570K|GPU=NVIDIA GeForce GTX 660 Ti|result=Running just fine! Great improvement from last test. No major slowdowns and no visible annonying glitches, at least with my DSP & graphics configuration.|tester=Thales}}
{{testing/entry|revision=4.0-4167|OS=Windows 8.1|CPU=Intel Core i5-3570K|GPU=NVIDIA GeForce GTX 660 Ti|result=Running just fine! Great improvement from last test. No major slowdowns and no visible annonying glitches, at least with my DSP & graphics configuration.|tester=Thales}}
{{testing/entry|revision=5.0|OS=Windows 10|CPU=Intel Core i7-6700K @ 4GHz|GPU=NVIDIA GeForce GTX 670 |result=Game runs perfectly! "need a strong CPU" 60 FPS all time no slowdowns, no problems at all.|tester=Peach}}
{{testing/entry|revision=5.0|OS=Windows 10|CPU=Intel Core i7-6700K @ 4.6GHz|GPU=NVIDIA GeForce GTX 1070|result="UPDATE" Just got my GTX 1070 and game is running on 4K 60 FPS !! + i7 OC at 4.6GHz
Game is running so perfect idk what to say.|tester=Peach}}
{{testing/end}}
{{testing/end}}


== Gameplay Videos ==
== Gameplay Videos ==
{{VideoGallery
{{VideoGallery
|vid1=LE8WgYQ5_0A|cap1=Metroid Prime 3: Corruption on Dolphin Wii/GC Emulator (720p HD) Full Speed
|vid1=AFu3p9n2jR8|cap1=Metroid Prime 3: Corruption on Dolphin the Wii Emulator (1080p HD)
|vid2=AFu3p9n2jR8|cap2=Metroid Prime 3: Corruption on Dolphin the Wii Emulator (1080p HD)
|vid2=LE8WgYQ5_0A|cap2=(r5063) Metroid Prime 3: Corruption on Dolphin Wii/GC Emulator (720p HD) Full Speed
|vid3=W-xz7pQ2hAk|cap3=Dolphin Emulator 3.5-367 - Metroid Prime 3: Corruption (1080p HD) - Nintendo Wii
|vid3=W-xz7pQ2hAk|cap3=Dolphin Emulator 3.5-367 - Metroid Prime 3: Corruption (1080p HD) - Nintendo Wii
|vid4=lB3rsn61Wec|cap4=Metroid Prime 3: Corruption - Gameplay Wii 4K 2160p60 (Dolphin 5.0)
}}
}}



Revision as of 22:16, 16 January 2018

Metroid Prime 3: Corruption
MetroidPrime3Corruption.jpg
Developer(s) Retro Studios
Publisher(s) Nintendo
Series Metroid, Metroid Prime
Platform(s) Wii
Release date(s) NA August 27, 2007
EU October 26, 2007
AUS November 8, 2007
JP March 6, 2008
Genre(s) First-person action-adventure, First-person shooter, 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
Dolphin Forum thread
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. 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.

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

Emulation Information

Constant Wii Remote Disconnects

Since 3.5-471, when using the MS Bluetooth Stack (the default bluetooth stack on Windows) Prime 3 will think that the Wii Remote is constantly disconnecting. Pressing a button on the Wii Remote 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 Compilation Stuttering

Metroid Prime 3: Corruption (Wii) is one of the most susceptible titles to shader compilation stuttering. The GC and Wii have no concept of shaders - everything is executed directly by the hardware without an intermediate programming language (API). Modern computers and mobile systems do not work in this way, requiring the use of shaders as an intermediary so your system's GPU can perform the tasks that the GC and Wii GPU performed directly. Shaders have to be generated though, and since GC/Wii games are not designed to create shaders ahead of time as a PC game would, when a new effect appears Dolphin has to delay the CPU thread while the GPU thread performs the compilation; a pause that does not exist on the consoles. For most games shader generation takes only a few milliseconds, but for a few demanding titles, the shaders that they generate are so large that they can result in noticeable stuttering, in severe cases pauses of over a second may occur.

Since 5.0-4869, this problem can be solved by enabling ubershaders. Changing GPU, updating GPU drivers, or updating Dolphin may invalidate the shader cache, requiring specialized shaders to be compiled again. Since 5.0-6461, Dolphin caches shader pipeline UIDs independently of the video backend and compiles them on game start. This allows cached shaders to work across different video backends, platforms, hardware configurations and even Dolphin versions as long as changes aren't made to Dolphin's actual shader pipeline. These shaders are compiled in the background when the game starts, which may cause stuttering for a short period. Enable Compile Shaders Before Starting to avoid this.

Problems

Visors

The Scan visor will only work if Store EFB Copies to Texture Only is disabled. Though Store EFB Copies to Texture Only is forced off by the GameINI, visor issues may still occur if the graphics configuration window is opened during gameplay. Disable Store EFB Copies to Texture Only in the Dolphin GUI to avoid any problems. Corrected with revised default setting handling.

The Black Bar

If the CPU and GPU threads of Dolphin desync too much during lag, a black bar may show up at the bottom of the screen. It 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. Because shader compilation stuttering is the main cause for these desyncs on a powerful computer, enabling Hybrid Mode Ubershaders or Exclusive Mode Ubershaders should help with preventing this issue. Enabling Single Core will remove any risk of this issue occurring. Fixed with Hybrid XFB in 5.0-5874.

Enhancements

Bloom Offset in IR>1

Prime 3 has noticeable bloom offset problems when playing above 1x Native internal resolution. 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.

Dot in IR>1

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.

Configuration

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

Wii Remote

Config Setting Notes
Enable Speaker Data Off Causes constant Wii Remote disconnects

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-21264 (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 Intel Core 2 Duo E7300 @ 2.6GHz NVIDIA GeForce GTX 275 Intro slow, but in game full speed.
r7111 Windows 7 Intel Core 2 Quad Q6600 ATI Radeon HD 5770 20/40 frames
r7478 Windows 7 Intel Core i7-2600K @ 3.4GHz AMD Radeon HD 6950 Works great. Real Wii Remote errors. Have to use emulated Wii Remote. Robodt7
r7670 Windows 7 Intel Core i5-2500K @ 4.1GHz AMD Radeon HD 6850 Runs flawlessly. 60FPS all the time. Still has Wii Remote control lag issues. Red blooming from light sources now fixed. MegaJump
r7670 Windows 7 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
4.0-2879 Windows 8.1 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
4.0-4167 Windows 8.1 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
5.0 Windows 10 Intel Core i7-6700K @ 4GHz NVIDIA GeForce GTX 670 Game runs perfectly! "need a strong CPU" 60 FPS all time no slowdowns, no problems at all. Peach
5.0 Windows 10 Intel Core i7-6700K @ 4.6GHz NVIDIA GeForce GTX 1070 "UPDATE" Just got my GTX 1070 and game is running on 4K 60 FPS !! + i7 OC at 4.6GHz

Game is running so perfect idk what to say.

Peach

Gameplay Videos