Metroid Prime 2: Echoes (Metroid Prime: Trilogy): Difference between revisions

Jump to navigation Jump to search
m (Oops!)
(→‎Gameplay Videos: add video)
(32 intermediate revisions by 8 users not shown)
Line 3: Line 3:
|developer = Retro Studios
|developer = Retro Studios
|publisher = Nintendo
|publisher = Nintendo
|series    = ''Metroid'', ''Metroid Prime''
|series    = Metroid, Metroid Prime
|released  = '''Original release'''<br/>{{vgrelease|NA=November 15, 2004|EU=November 26, 2004|AUS=December 2, 2004}}{{vgrelease|JP=May 26, 2005}}'''''Metroid Prime: Trilogy'''''<br/>{{Vgrelease|NA=August 24, 2009|EU=September 4, 2009|AUS=October 15, 2009}}
|released  = '''Original release'''<br/>{{vgrelease|NA=November 15, 2004|EU=November 26, 2004|AUS=December 2, 2004|JP|May 26, 2005}}'''''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, Multiplayer (4)
|modes    = Single-player, Multiplayer (4)
|input    = Wii Remote + Nunchuk
|input    = Wii Remote + Nunchuk
|forumlink = http://forums.dolphin-emu.org/Thread-wii-metroid-prime-trilogy--26043
|wikipedia = Metroid Prime: Trilogy
|wikipedia = Metroid Prime: Trilogy
|forumlink = http://forums.dolphin-emu.org/Thread-wii-metroid-prime-trilogy--26043
}}
}}


Line 24: Line 24:
<div style="clear:left;"></div>
<div style="clear:left;"></div>


== Problems ==
== Emulation Information ==
 
=== Performance ===
Performance in general seems reduced compared to the game's GameCube counterpart. This may be related to the higher resolution textures and various new screen effects added for the Trilogy versions.
 
=== 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.
 
=== 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) this game 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.
<!-- 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.


=== Bloom Offset ===
{{Problems/Shader Compilation Stuttering}}
Like Prime 3 and all the Trilogy games, Prime 2 Trilogy has bloom offset problems. Fortunately, it is not very noticeable with this game. There is no known solution to this issue. See {{issue|5573}}.


=== Dot ===
== Problems ==
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.
{{Problems|{{#vardefineecho:problems|
{{image|MP2GC Thedot zoom.png|The dot, zoomed in 8x|br}}
=== <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 default option handling revisions.
=== 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 Black Bar ===
=== <s>The Black Bar</s> ===
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|MP2Tri NoSquish.jpg|Correct emulation}}
{{image|MP2Tri NoSquish.jpg|Correct emulation}}
{{image|MP2Tri Squish.jpg|Black bar and squishing|br}}
{{image|MP2Tri Squish.jpg|Black bar and squishing|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 in OpenGL. Even the strongest computers are affected by this issue, and there is no solution with the OpenGL backend at this time. D3D is not affected by this problem in this game. Fixed by {{revision|4.0-5124}}.
 
== Enhancements ==
=== Bloom Offset in IR>1 ===
<!-- Shared problem with other [[Metroid Trilogy]] games -->
Like Prime 3 and all the Trilogy games, Prime 2 Trilogy has bloom offset problems. Fortunately, it is not very noticeable with this game. There is no known solution to this issue. See {{issue|5573}}.
 
=== 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.
{{image|MP2GC 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
|enablespeakerdata      = Off
|xfbnotes = Needed to prevent the black bar
|enablespeakerdatanotes = Causes constant Wii Remote disconnects
|efb2texonly = Off
|efb2texonlynotes = Needed to avoid visor issues
|enablespeakerdata      = Disabled
|enablespeakerdatanotes = Causes constant wiimote disconnects
}}
}}


Line 72: Line 69:
{{VersionCompatibility}}
{{VersionCompatibility}}
<!--Use this template for compatibility entries: {{VersionCompatibilityVersion|revision|****|notes}}-->
<!--Use this template for compatibility entries: {{VersionCompatibilityVersion|revision|****|notes}}-->
{{VersionCompatibilityVersion|7689|***}}
{{VersionCompatibilityVersion|7689|***|}}
{{VersionCompatibilityVersion|4.0-5384|****}}
{{VersionCompatibilityVersion|5.0-4869|****|Shader Compilation Stuttering resolved with Ubershaders}}
{{VersionCompatibilityClose}}
{{VersionCompatibilityClose}}


Line 79: Line 76:
{{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=7689|OS=Windows 7 x64|CPU=Intel Core i5-2500K @ 4.4GHz|GPU=NVIDIA GeForce GTS 250|result=Close to perfect -> constant 60FPS, 1280x720, 3xNative textures and DSP-HLE sound (still must use dol swap though)|tester=Zlutz}}
{{testing/entry|revision=7689|OS=Windows 7|CPU=Intel Core i5-2500K @ 4.4GHz|GPU=NVIDIA GeForce GTS 250|result=Close to perfect -> constant 60FPS, 1280x720, 3xNative textures and DSP-HLE sound (still must use dol swap though)|tester=Zlutz}}
{{testing/entry|revision=3.0-766|OS=Windows 7 x64|CPU=Intel Core i7-3770K @ 4.4GHz|GPU=AMD Radeon HD 6970|result=DX11 at 1900x1200 (using internal resolution auto, 4xAA), averages 50FPS.  EFB-copy-to-RAM must be used 100% of the time for the scan visor to function (contrast to MP1 where it is only required for the rarely-used x-ray visor), but fastest cache option can be used (causes very minor graphical glitches).  "Skip Destination Alpha Pass" also breaks the scan visor and should be left off.  "Accurate V-Beam" (in right-click options) provides noticeable speedup in large rooms with no ill effect.  DSP-HLE works fine, except for very occasional loss of BGM (can be resolved by save/load or reset); DSP-LLE does not drop BGM but instead causes crackling and clicking sounds whenever framerate drops below 60FPS.  OpenMP texture decoder, cache display lists, and disable fog/per-pixel-depth are all recommended for slight speedup.  DOL swap still required to run.|tester=anon}}
{{testing/entry|revision=3.0-766|OS=Windows 7|CPU=Intel Core i7-3770K @ 4.4GHz|GPU=AMD Radeon HD 6970|result=DX11 at 1900x1200 (using internal resolution auto, 4xAA), averages 50FPS.  EFB-copy-to-RAM must be used 100% of the time for the scan visor to function (contrast to MP1 where it is only required for the rarely-used x-ray visor), but fastest cache option can be used (causes very minor graphical glitches).  "Skip Destination Alpha Pass" also breaks the scan visor and should be left off.  "Accurate V-Beam" (in right-click options) provides noticeable speedup in large rooms with no ill effect.  DSP-HLE works fine, except for very occasional loss of BGM (can be resolved by save/load or reset); DSP-LLE does not drop BGM but instead causes crackling and clicking sounds whenever framerate drops below 60FPS.  OpenMP texture decoder, cache display lists, and disable fog/per-pixel-depth are all recommended for slight speedup.  DOL swap still required to run.|tester=anon}}
{{testing/entry|revision=4.0-2826|OS=Windows 7 x64|CPU=Intel Core i7-4790K @ 4.6GHz|GPU=AMD Radeon HD 7970|result=OpenGL at 1920x1080 (3x internal res), no AA, 4x AF, works consistently at 58-60FPS so far - I will update if I see similar drops like I saw in MP1|tester=anon}}
{{testing/entry|revision=4.0-2826|OS=Windows 7|CPU=Intel Core i7-4790K @ 4.6GHz|GPU=AMD Radeon HD 7970|result=OpenGL at 1920x1080 (3x internal res), no AA, 4x AF, works consistently at 58-60FPS so far - I will update if I see similar drops like I saw in MP1|tester=anon}}
{{testing/entry|revision=4.0-4843|OS=Windows 7 x64|CPU=Intel Core i5-750 @ 2.66GHz|GPU=NVIDIA GeForce GTX 680|result=ES_Launch problems now solved, no problems with speaker data. Direct 3D, EFB to RAM  used. Frequent drops to 25FPS and I must go to windowed then fullscreen again to gain 50FPS. Everything OK otherwise.|tester=Paulli}}
{{testing/entry|revision=4.0-4843|OS=Windows 7|CPU=Intel Core i5-750 @ 2.66GHz|GPU=NVIDIA GeForce GTX 680|result=ES_Launch problems now solved, no problems with speaker data. Direct 3D, EFB to RAM  used. Frequent drops to 25FPS and I must go to windowed then fullscreen again to gain 50FPS. Everything OK otherwise.|tester=Paulli}}
{{testing/entry|revision=4.0-5384|OS=Windows Server 2012 x64|CPU=AMD FX-8350 @ 4.6GHz|GPU=AMD Radeon HD 7970|result=D3D @1920x1080 (3x IR), no AA, 1x AF, playing at PAL50. Runs very nicely, minor FPS drops when entering water and in some places, otherwise constant 50FPS. Played all the way through without major glitches.|tester=XorUnison}}
{{testing/entry|revision=4.0-5384|OS=Windows Server 2012|CPU=AMD FX-8350 @ 4.6GHz|GPU=AMD Radeon HD 7970|result=D3D @1920x1080 (3x IR), no AA, 1x AF, playing at PAL50. Runs very nicely, minor FPS drops when entering water and in some places, otherwise constant 50FPS. Played all the way through without major glitches.|tester=XorUnison}}
{{testing/entry|revision=5.0-rc-34|OS=SteamOS 2.60|CPU=Intel Core i3-4170 @ 3.7GHz|GPU=NVIDIA GeForce GTX 750 Ti|result=OGL, 3x IR, no other enhancements, NTSC-U. Fullspeed aside from portal transitions (where crackling audio is the only noticeable effect). No glitches as far as I could tell.|tester=monojin}}
{{testing/end}}
{{testing/end}}


Line 89: Line 87:
{{VideoGallery
{{VideoGallery
|vid1=bNsglEfBotE|cap1=Metroid Prime Trilogy (MP1 & MP2) HD Gameplay
|vid1=bNsglEfBotE|cap1=Metroid Prime Trilogy (MP1 & MP2) HD Gameplay
|vid2=rBlDZz1_D2Y|cap2=Metroid Prime: Trilogy - Dolphin Emulator 5.0-12656 [1080p HD] - Nintendo Wii
}}
}}
{{Navigation Metroid}}
{{Navigation/Metroid}}


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

edits

Navigation menu