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

Jump to navigation Jump to search
Dot workaround
m (Text replacement - "ShaderCompStuttering" to "Shader Compilation Stuttering")
(Dot workaround)
(30 intermediate revisions by 12 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 ==
=== Constant Wii Remote Disconnects ===
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.
{{Problems/Shader Compilation Stuttering}}
{{Problems/Shader Compilation Stuttering}}


== Problems ==
== Problems ==
=== Constant Wii Remote Disconnects ===
{{Problems|{{#vardefineecho:problems|
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.
=== <s>Visors</s> ===
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.


=== Bloom Offset ===
=== <s>The Black Bar</s> ===
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}}.
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 Bloom1.png|Example of the bloom offset}}
{{image|MP3 Bloom2.png|Another example of the offset|br}}


=== Visors ===
{{image|MP3 NoSquish.jpg|Correct emulation}}
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.
{{image|MP3 Squish.jpg|Black bar with the squished image|br}}


=== 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.
{{image|MP3-Thedot-zoom.png|The dot, zoomed in 8x|br}}


=== The Black Bar ===
== Enhancements ==
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.
=== 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}}.
{{image|MP3 Bloom1.png|Example of the bloom offset}}
{{image|MP3 Bloom2.png|Another example of the offset|br}}


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].
=== 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. It can be hidden along with the helmet and visor display in the game's options.  


{{image|MP3 NoSquish.jpg|Correct emulation}}
Another workaround for this problem is to put these custom textures into the Dolphin Emulator\Load\Textures folder and enabling the '''Load Custom Textures''' option in the advanced graphics settings.  
{{image|MP3 Squish.jpg|Black bar with the squished image|br}}


=== {{s}}Savestates{{/s}} ===
https://cdn.discordapp.com/attachments/559645428451246090/802436195375382538/Dot_Fix.zip
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).
{{image|MP3-Thedot-zoom.png|The dot, zoomed in 8x|br}}
 
=== {{s}}Pixelation Glitches{{/s}} ===
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]
{{image|MP3-Pixelboxes-cropzoom.jpg|Example of the pixelation, top half is blurred|br}}
 
=== {{s}}Refraction Slowdown{{/s}} ===
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}}.


=== {{s}}Blue Startup Video{{/s}} ===
=== HD Textures ===
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}}.
[https://forums.dolphin-emu.org/showthread.php?tid=59035 Metroid Prime Trilogy - HD Interface Textures]. This texture pack works with the Trilogy and the standalone GameCube/Wii titles.
{{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
|shadercomp            = Asynchronous (Ubershaders)
|xfbnotes = Needed to prevent the black bar
|shadercompnotes        = 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 67:
{{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}}
{{VersionCompatibilityVersion|5.0-11518|*****|Since prior to this revision}}
{{VersionCompatibilityClose}}
{{VersionCompatibilityClose}}


Line 85: Line 79:
{{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)
|vid5=_CZXmnv3Sy8|cap5=Metroid Prime 3: Corruption - Dolphin Emulator 5.0-12656 [1080p HD] - Nintendo Wii
}}
}}


Navigation menu