10
edits
Metroid Prime 3: Corruption (Wii): Difference between revisions
Jump to navigation
Jump to search
Metroid Prime 3: Corruption (Wii) (view source)
Revision as of 15:16, 23 January 2021
, 23 January 2021Dot workaround
No edit summary |
TowerTowel (talk | contribs) (Dot workaround) |
||
| (11 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{Infobox VG | {{Infobox VG | ||
|image = [[File:MetroidPrime3Corruption.jpg|300px]] | |||
|image = [[File:MetroidPrime3Corruption.jpg|300px | |||
|developer = Retro Studios | |developer = Retro Studios | ||
|publisher = Nintendo | |publisher = Nintendo | ||
|series = | |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 | ||
| Line 20: | Line 19: | ||
== Emulation Information == | == Emulation Information == | ||
=== Constant Wii Remote Disconnects === | === 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}} | ||
| Line 38: | Line 37: | ||
== Enhancements == | == Enhancements == | ||
=== Bloom Offset === | === 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}}. | 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 Bloom1.png|Example of the bloom offset}} | ||
{{image|MP3 Bloom2.png|Another example of the offset|br}} | {{image|MP3 Bloom2.png|Another example of the offset|br}} | ||
=== Dot === | === 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. | 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. | ||
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. | |||
https://cdn.discordapp.com/attachments/559645428451246090/802436195375382538/Dot_Fix.zip | |||
{{image|MP3-Thedot-zoom.png|The dot, zoomed in 8x|br}} | {{image|MP3-Thedot-zoom.png|The dot, zoomed in 8x|br}} | ||
=== HD Textures === | |||
[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. | |||
== 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 | ||
| | |shadercomp = Asynchronous (Ubershaders) | ||
| | |shadercompnotes = Needed to avoid shader compilation stuttering | ||
|enablespeakerdata = Off | |enablespeakerdata = Off | ||
|enablespeakerdatanotes = Causes constant Wii Remote disconnects | |enablespeakerdatanotes = Causes constant Wii Remote disconnects | ||
| Line 62: | Line 68: | ||
{{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-4869|****|Shader Compilation Stuttering resolved with Ubershaders}} | ||
{{VersionCompatibilityVersion|5.0-11518|*****|Since prior to this revision}} | |||
{{VersionCompatibilityClose}} | {{VersionCompatibilityClose}} | ||
| Line 72: | 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 | {{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 @ 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}} | ||
| Line 85: | Line 92: | ||
|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) | |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 | |||
}} | }} | ||