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

Jump to navigation Jump to search
(RegExp Mass Edit, line break cleanup, Template:Navigation fix)
(→‎Gameplay Videos: add video)
(22 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{Infobox VG
{{Infobox VG
|title    = Metroid Prime 3: Corruption
|image    = [[File:MetroidPrimeTrilogy.jpg|300px]]
|image    = [[File:MetroidPrimeTrilogy.jpg|300px]]
|developer = Retro Studios
|developer = Retro Studios
|publisher = Nintendo
|publisher = Nintendo
|series    = ''Metroid'', ''Metroid Prime''
|series    = Metroid, Metroid Prime
|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}}
|released  = '''Original release'''<br/>{{vgrelease|NA=August 27, 2007|EU=October 26, 2007|AUS=November 8, 2007|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, First-person shooter, Action-adventure
|genre    = First-person action-adventure, First-person shooter, Action-adventure
|modes    = Single-player
|modes    = Single-player
Line 17: Line 16:


== Game Pages ==
== Game Pages ==
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.
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.


<div style="float:left; padding:3px;">[[File:MPT Game Pages Trilogy.png|link=Metroid Prime: Trilogy]]</div>
<div style="float:left; padding:3px;">[[File:MPT Game Pages Trilogy.png|link=Metroid Prime: Trilogy]]</div>
Line 25: Line 24:


== Emulation Information ==
== Emulation Information ==
=== Constant Wii Remote Disconnects ===
<!-- Copied from [[Metroid Prime: Trilogy#Constant Wii Remote Disconnects]] -->
When using the MS Bluetooth Stack (the default Bluetooth stack on Windows) the game 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. Disable '''Enable Speaker Data''' to remedy this problem. It's a problem bound to PC hardware and driver, you can also try [[Bluetooth Passthrough]], or follow this [[Wii Remote Plus (RVL-CNT-01-TR) Connection Guide#Windows|Wii Remote -TR Connection Guide]] anyhow to avoid the MS Bluetooth stack. DolphinBar is another viable solution for this problem.
{{Problems/Shader Compilation Stuttering}}
{{Problems/Shader Compilation Stuttering}}


== Problems ==
== Problems ==
{{Problems|
{{Problems|{{#vardefineecho:problems|
=== Constant Wii Remote Disconnects ===
=== <s>Visors</s> ===
Since {{revision|3.5-471}}, when using the MS Bluetooth Stack (the default Bluetooth stack on Windows) the game 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. Disable "Enable Speaker Data" to solve this problem, or avoid the MS Bluetooth stack by using the DolphinBar or the Toshiba Stack (for instruction of which is available at [[Wii Remote Plus (RVL-CNT-01-TR) Connection Guide#Windows]]).
 
=== 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. The only solution is to disable "Scaled EFB Copy", but this has some issues of its own. See {{issue|5573}}.
If it's played under native resolution, the bloom effect will have the desired effect due to the low pixel count on screen, nonetheless.
{{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.
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.
{{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.
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].
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]. 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}}


}}
}}}}
 
== Enhancements ==
=== Bloom Offset in IR>1 ===
''Metroid Prime 3'' has been prominent in using blooming effects unlike the other Metroid Prime: Trilogy games, and therefore the blooming offset problem in this game became more noticeable than others. It will have several copies of the bloom spread out from the source, and can be very distracting. Disabling '''Scaled EFB Copy''' in Dolphin's settings will influence how the blooming effects should look, but this has some issues on its own, such as upper-left part of the screen become pixelated. It's a problem belonging to resolutions that the real Wii never had.
{{image|MP3 Bloom1.png|Example of the bloom offset}}
{{image|MP3 Bloom2.png|Another example of the offset|br}}
 
=== Dot in IR>1 ===
<!-- Shared problem with other [[Metroid Prime: Trilogy]] games -->
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 (Hit '''"1"''' on your Wii Remote then point at wrench icon on the bottom left of the screen to bring up the option screen then go to monitor icon on the right of the screen, then set both "Helmet Opacity" and "Visor Opacity" to 0). It's a problem belonging to resolutions that the real Wii never had.
{{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
|xfb = Virtual
|xfbnotes = Needed to prevent the black bar
|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 72: Line 72:
{{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 77: Line 78:
{{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=3.0-735|OS=Windows 7|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 60FPS but drops are common. I experienced all the problems listed above.|tester=MaJoR}}
{{testing/entry|revision=3.0-735|OS=Windows 7|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 60FPS but drops are common. I experienced all the problems listed above.|tester=MayImilae}}
{{testing/entry|revision=3.5-392|OS=Windows 7|CPU=Intel Core i7-2600K|GPU=NVIDIA GeForce GTX 560|result="Accurate VBeam emulation" enabled in properties file. Direct3D11 backend, EFB to texture, 2.5x resolution, DSP HLE and XAudio2. Tested in first Norion section - almost perfect emulation, slight slowdown when using Scan Visor, and the odd tiny audio blip. Dot glitch present. (PAL version.)|tester=-}}
{{testing/entry|revision=3.5-392|OS=Windows 7|CPU=Intel Core i7-2600K|GPU=NVIDIA GeForce GTX 560|result="Accurate VBeam emulation" enabled in properties file. Direct3D11 backend, EFB to texture, 2.5x resolution, DSP HLE and XAudio2. Tested in first Norion section - almost perfect emulation, slight slowdown when using Scan Visor, and the odd tiny audio blip. Dot glitch present. (PAL version.)|tester=-}}
{{testing/entry|revision=5.0-10155|OS=Windows 10|CPU=Intel Core i7-7800X @ 4GHz|GPU=NVIDIA GeForce GTX 960|result=Virtually perfect on Vulkan with Ubershaders, other than the problems already listed. Default settings with the latest dev versions, loading custom textures, 3x native res, and only the occasional stutter (often only related to other processes on my system), even when loading rooms. Enabled WiiMote speaker data and didn't get disconnects with DolphinBar, but didn't seem to get any sound out of it anyway.|tester=Malkierian}}
{{testing/end}}
{{testing/end}}


== Gameplay Videos ==
== Gameplay Videos ==
<!--A full list of options is available at Template:VideoGallery/doc-->
{{VideoGallery
|vid1=rBlDZz1_D2Y|cap1=Metroid Prime: Trilogy - Dolphin Emulator 5.0-12656 [1080p HD] - Nintendo Wii
}}
 
{{Navigation/Metroid}}
{{Navigation/Metroid}}


[[Category:Wii games]]
[[Category:Wii games]]
2,225

edits

Navigation menu