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

Jump to navigation Jump to search
m
no edit summary
m (Text replacement - "({{VersionCompatibilityVersion\|[^\|]*\|[^\|]*)}}" to "$1|}}")
mNo edit summary
(30 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 18: Line 17:
''Metroid Prime 3'' was also included in [[Metroid Prime: Trilogy]], which includes updated versions of its prequels: [[Metroid Prime]] and [[Metroid Prime 2: Echoes]].
''Metroid Prime 3'' was also included in [[Metroid Prime: Trilogy]], which includes updated versions of its prequels: [[Metroid Prime]] and [[Metroid Prime 2: Echoes]].


== Problems ==
== Emulation Information ==
=== 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 wiimote 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.


=== Shader Compilation Stuttering ===
{{Problems/Shader Compilation Stuttering}}
The ''Metroid Prime'' games are some of the most susceptible titles to shader compilation stuttering, thanks to a combination of very complex effects and dynamic loading. The GC and Wii have no concept of shaders - everything runs directly "on the metal" without any APIs. Modern desktop and phone 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. But shaders have to be created, 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 the ''Metroid Prime'' series and a few other demanding titles, the shaders that they generate are so large that they can result in noticeable stuttering.


Eventually stuttering will reduce as a shader cache is built up, but there is no solution to this problem at this time.
== Problems ==
 
{{Problems|{{#vardefineecho:problems|
=== Bloom Offset ===
=== <s>Visors</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}}.
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.
{{image|MP3 Bloom1.png|Example of the bloom offset}}
{{image|MP3 Bloom2.png|Another example of the offset|br}}
 
=== 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.


=== Dot ===
=== <s>The Black Bar</s> ===
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.
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-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].


{{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 wiimote 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
|enablespeakerdata      = Off
|efb2texonlynotes = Needed to avoid visor issues
|enablespeakerdatanotes = Causes constant Wii Remote disconnects
|enablespeakerdata      = Disabled
|enablespeakerdatanotes = Causes constant wiimote disconnects
}}
}}


Line 77: 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 82: Line 66:
{{testing/start}}
{{testing/start}}
<!--Use this template for test entries: {{testing/entry|revision=|OS=|CPU=|GPU=|result=|tester=}}-->
<!--Use this template for test entries: {{testing/entry|revision=|OS=|CPU=|GPU=|result=|tester=}}-->
{{testing/entry|revision=5442|OS=Windows 7 x64|CPU=Intel Core 2 Duo E7300 @ 2.6GHz|GPU=NVIDIA GeForce GTX 275|result=Intro slow, but in game full speed.|tester=}}
{{testing/entry|revision=5442|OS=Windows 7|CPU=Intel Core 2 Duo E7300 @ 2.6GHz|GPU=NVIDIA GeForce GTX 275|result=Intro slow, but in game full speed.|tester=}}
{{testing/entry|revision=7111|OS=Windows 7 x64|CPU=Intel Core 2 Quad Q6600|GPU=ATI Radeon HD 5770|result= 20/40 frames|tester=}}
{{testing/entry|revision=7111|OS=Windows 7|CPU=Intel Core 2 Quad Q6600|GPU=ATI Radeon HD 5770|result= 20/40 frames|tester=}}
{{testing/entry|revision=7478|OS=Windows 7 x64|CPU=Intel Core i7-2600K @ 3.4GHz|GPU=AMD Radeon HD 6950|result=Works great. Real Wii Remote errors. Have to use emulated Wii Remote.|tester=Robodt7}}
{{testing/entry|revision=7478|OS=Windows 7|CPU=Intel Core i7-2600K @ 3.4GHz|GPU=AMD Radeon HD 6950|result=Works great. Real Wii Remote errors. Have to use emulated Wii Remote.|tester=Robodt7}}
{{testing/entry|revision=7670|OS=Windows 7 x64|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 x64|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 x64|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 x64|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)
}}
}}


6,576

edits

Navigation menu