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

Jump to navigation Jump to search

Metroid Prime (Metroid Prime: Trilogy) (view source)

Revision as of 15:18, 23 January 2021

3,001 bytes added ,  23 January 2021
m
→‎Dot in IR>1
(4.0 Cleanup)
(98 intermediate revisions by 24 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 17, 2002}}{{vgrelease|JP=February 28, 2003|EU=March 21, 2003|AUS=April 3, 2003}}'''''Metroid Prime: Trilogy'''''<br/>{{Vgrelease|NA=August 24, 2009|EU=September 4, 2009|AUS=October 15, 2009}}
|released  = '''Original release'''<br/>{{vgrelease|NA=November 17, 2002}}{{vgrelease|JP=February 28, 2003|EU=March 21, 2003|AUS=April 3, 2003}}'''''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
Line 22: Line 22:
<div style="float:left; padding:3px;">[[File:MPT Game Pages Prime3.png|link=Metroid Prime 3: Corruption (Metroid Prime: Trilogy)]]</div>
<div style="float:left; padding:3px;">[[File:MPT Game Pages Prime3.png|link=Metroid Prime 3: Corruption (Metroid Prime: Trilogy)]]</div>
<div style="clear:left;"></div>
<div style="clear:left;"></div>
== 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 ==
== Problems ==
{{Problems|{{#vardefineecho:problems|
=== <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.


=== Performance ===
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}}.
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.


=== Black Bar and Severe Stutters ===
At seemingly random points throughout the game, the game will freeze for an instant, flashing to black and "redrawing". When it comes back, a black bar will be at the bottom of the screen, taking up 15% of the screen space and "squishing" the game in the remaining space. From thorough testing, this apparently occurs whenever the emulator stops the GPU thread for a split-second, causing the GPU and CPU threads to desync. Most games don't care about this, but Prime freaks out and creates this error. Creating a new shadercache, from first run of the game or from going into a new area, will immediately cause the desync, as well as going in and out of fullscreen and even taking a screenshot. Building up a shadercache of an area helps, but it will still desync if a new effect or region is loaded. Playing with Dual Core disabled or using Sync GPU Thread is the only solution at this time. See {{issue|5185}}.
*PAL users can disable "EuRGB60 Mode (PAL60)" in the Wii settings to prevent this issue.
{{image|MP1Tri NoSquish.jpg|Correct emulation}}
{{image|MP1Tri NoSquish.jpg|Correct emulation}}
{{image|MP1Tri Squish.jpg|Black bar and squishing|br}}
{{image|MP1Tri Squish.jpg|Black bar and squishing|br}}


=== Constant Wiimote Disconnects ===
As for version 5.0, to remove the black bar simply go to Configuration, Wii tab, and uncheck "Use PAL60 Mode (EuRGB60)"
Since {{revision|3.5-471}}, the game will think that the wiimote is constantly disconnecting. Pressing Alt-F5 will restore it, but it will disconnect again seconds later. Disable "Enable Speaker Data" to solve this problem.


=== Micro-stuttering ===
}}}}
All of the Prime games suffer from micro-stuttering: small stops in the video that can become very annoying. It occurs in all graphics backends, but the OpenGL backend has consistently been the most resistant to the problem. Its severity varies depending on the revision and settings used, so if you want to play the game you should try a wide variety of combinations.


=== Bloom Offset ===
== Enhancements ==
Like Prime 3 and all the Trilogy games, Prime 1 Trilogy has bloom offset problems. Fortunately, it is not very noticeable with this game. The only solution is to disable Scaled EFB copies, which creates issues of its own. See {{issue|5573}}.
=== Bloom Offset in IR>1 ===
Like Prime 3 and all the Trilogy games, Prime 1 Trilogy has bloom offset problems when playing above 1x Native internal resolution. Fortunately, it is not very noticeable with this game. The only solution is to disable Scaled EFB copies, which creates issues of its own. See {{issue|5573}}.
{{image|MP1Tri-Bloom.png|Example of the bloom offset|br|width=200}}
{{image|MP1Tri-Bloom.png|Example of the bloom offset|br|width=200}}


=== Refraction Slowdown ===
=== Dot in IR>1 ===
Refraction effects, such as raindrops on Samus' visor, 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. D3D11 and D3D9 are not affected by this problem in this game.
<!-- Shared problem with other [[Metroid Prime: Trilogy]] games -->
When playing above 1x Native internal resolution, there is a dot in the very center of the screen. It's small and easy to ignore, but it's always there.  This problem did not appear in the original game [[Metroid Prime (GC)|Metroid Prime]] for GameCube. It can be hidden along with the helmet and visor display in the game's options.


=== Visors ===
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.  
Visors will only work if EFB to Ram is enabled. Though EFB to Ram is forced by the GameINI, visor corruption may still occur. Turn on EFB to Ram in the Dolphin GUI to avoid any problems.


=== Dot ===
https://cdn.discordapp.com/attachments/559645428451246090/802436195375382538/Dot_Fix.zip
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}}
{{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
|efbcopy = RAM
|efbcopynotes = Needed to avoid visor issues
|enablespeakerdata      = Off
|enablespeakerdata      = Off
|enablespeakerdatanotes = Causes constant Wiimote disconnects
|enablespeakerdatanotes = Prevents constant Wii Remote disconnects
}}
}}


== Version Compatibility ==
== Version Compatibility ==
{{VersionCompatibility}}
{{VersionCompatibility}}
<!--Use this template for compatibility entries: {{VersionCompatibilityVersion|revision|****}}-->
<!--Use this template for compatibility entries: {{VersionCompatibilityVersion|revision|****|notes}}-->
{{VersionCompatibilityVersion|7689|***}}
{{VersionCompatibilityVersion|7689|***|}}
{{VersionCompatibilityVersion|5.0-4869|****|Shader Compilation Stuttering resolved with Ubershaders}}
{{VersionCompatibilityClose}}
{{VersionCompatibilityClose}}


Line 72: Line 79:
{{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=7714|OS=Windows 7 x64|CPU=AMD Phenom II X4 980 @ 4.2GHz|GPU=nVidia GeForce 8800 GT|result=DX9, 1.5x Resolution, 4x SSAA, 8x AF runs at 90-100%.  HLE works with little to no issues.  Use Accurate VBeam Emulation for a nice speedup.  Very well emulated in current versions.  MUST use dol swap to get working.|tester=Keller999}}
{{testing/entry|revision=7714|OS=Windows 7|CPU=AMD Phenom II X4 980 @ 4.2GHz|GPU=NVIDIA GeForce 8800 GT|result=DX9, 1.5x Resolution, 4x SSAA, 8x AF runs at 90-100%.  HLE works with little to no issues.  Use Accurate VBeam Emulation for a nice speedup.  Very well emulated in current versions.  MUST use dol swap to get working.|tester=Keller999}}
{{testing/entry|revision=3.0-694|OS=Windows 7 x64|CPU=AMD Phenom II X6 1090T @ 3.2GHz|GPU=AMD Radeon HD 6870|result=For any Resolution up to 2.5x, any AA up to max, any AF up to 8x: With EFB->Texture, runs at ~30-45fps. With EFB->RAM, runs at ~7-10fps. EFB->RAM needed for X-Ray Visor, otherwise it's just a white screen. Thermal Visor works fine with EFB->Texture. No other settings seem to have any real effect on the framerate, although enabling Accurate VBeam Emulation in the properties does provide a speedup on the map screen, from ~10fps OGL and ~20fps DX9/11 to ~45fps with any settings.
{{testing/entry|revision=3.0-694|OS=Windows 7|CPU=AMD Phenom II X6 1090T @ 3.2GHz|GPU=AMD Radeon HD 6870|result=For any Resolution up to 2.5x, any AA up to max, any AF up to 8x: With EFB->Texture, runs at ~30-45FPS. With EFB->RAM, runs at ~7-10FPS. EFB->RAM needed for X-Ray Visor, otherwise it's just a white screen. Thermal Visor works fine with EFB->Texture. No other settings seem to have any real effect on the framerate, although enabling Accurate VBeam Emulation in the properties does provide a speedup on the map screen, from ~10FPS OGL and ~20FPS DX9/11 to ~45FPS with any settings.
(x64 Release, git master rev bfde41895f52 + ES_LAUNCH rev 52def7cebd32, compiled w/ MS VS 2010.)|tester=eyeonus}}
(x64 Release, git master rev bfde41895f52 + ES_LAUNCH rev 52def7cebd32, compiled w/ MS VS 2010.)|tester=eyeonus}}
{{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), game completed averaging 50-60fps, except for areas where X-Ray visor is required: EFB>RAM must be used, decreasing performance to 30-40fps.  Recommend using save-states to switch EFB>RAM off except when x-ray visor is used (not very often).  Other slowdowns common when entering/existing water, likely due to visor droplet effect.  "Accurate V-Beam" in right-click options provides noticeable speedup in large rooms.  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 60.  OpenMP texture decoder and disable fog/pixeldepth recommended for slight speedup, no ill effects observed.  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), game completed averaging 50-60FPS, except for areas where X-Ray visor is required: EFB>RAM must be used, decreasing performance to 30-40FPS.  Recommend using save-states to switch EFB>RAM off except when x-ray visor is used (not very often).  Other slowdowns common when entering/existing water, likely due to visor droplet effect.  "Accurate V-Beam" in right-click options provides noticeable speedup in large rooms.  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 60.  OpenMP texture decoder and disable fog/pixeldepth recommended for slight speedup, no ill effects observed.  DOL swap still required to run.|tester=anon}}
{{testing/entry|revision=3.5-379|OS=Windows 7 x64|CPU=Intel Core i5-2500K @ 4.3GHz|GPU=nVidia GeForce GTX 680 x2|result=100% emulation, there's no stuttering or lagging. Minor problems, such as 3 pixels at the middle of the screen. It's a bit annoying but easy to ignore. Nvidia 3D vision isn't working, possibly a Dolphin problem. Settings used: Direct3D9, no AA, no Anisotropic filtering, HLE audio (seems to work right, without any problems), 1440x900 fullscreen resolution.|tester=Megamew28}}
{{testing/entry|revision=3.5-379|OS=Windows 7|CPU=Intel Core i5-2500K @ 4.3GHz|GPU=NVIDIA GeForce GTX 680|result=100% emulation, there's no stuttering or lagging. Minor problems, such as 3 pixels at the middle of the screen. It's a bit annoying but easy to ignore. NVIDIA 3D vision isn't working, possibly a Dolphin problem. Settings used: Direct3D9, no AA, no Anisotropic filtering, HLE audio (seems to work right, without any problems), 1440x900 fullscreen resolution.|tester=Megamew28}}
{{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 - There was a halo around Samus during elevator cutscenes and in the menu screen that I did not see in 4.0-2591, I saw drops in FPS when entering or exiting water and MAJOR drops when fighting meta ridley (25FPS at times), other than than such a great experience playing MP1 in 1080p|tester=anon}}
{{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, much like in Metroid Prime 2, otherwise constant 50FPS. Played all the way through without major glitches. Very close to being perfect.|tester=XorUnison}}
{{testing/entry|revision=5.0-1637|OS=Windows 10|CPU=Intel Core i7-4790 @ 3.6GHz|GPU=NVIDIA GeForce GTX 970|result=Both OpenGL and D3D11 @ 1920x1080 (3x IR), no AA, 16x AF. Mostly stable framerate at 60 FPS with the occasional drop. As expected, with the External Frame Buffer (XFB) disabled, a large black bar appears at the bottom of the screen and stretches the rest of the image. While setting the XFB to Virtual does fix this particular issue, there is constant flickering and the framerate drops somewhat. Setting the XFB to Real, however, causes severe graphical issues, and the framerate drops to around 4 FPS. As a result the game is unplayable for me.|tester=LifeWulf}}
{{testing/entry|revision=5.0-1943|OS=Windows 10|CPU=Intel Core Xeon-5670 @ 4.8GHz|GPU=NVIDIA GeForce GTX 1070|result=D3D12(Experimental) @ 1920x1080 (3x IR), no AA, 16x AF. High improvement in stability with less and shorter framerate drops than other rendering modes.|tester=Searanger}}
{{testing/entry|revision=5.0-2612|OS=Windows 8.1|CPU=Intel Core i7-5820k @ 3.8GHz|GPU=AMD R9 Fury X|result=Vulkan(Experimental) @ 3440x1440 (black bars to keep 16:9 aspect) (Window Size IR), 2x MSAA, 16x AF. Tested with European release. I encountered no problems during my run. Virtual XFB worked well, no flickering or other visible artifacts. Still experiences a few stutters when building shaders but it's almost perfect now.|tester=Oceankhayne}}
{{testing/entry|revision=5.0-4322|OS=Windows 10|CPU=Intel Core i7-4790K @ 4GHz|GPU=NVIDIA GeForce GTX 1070|result=80% run w/ Vulkan at 3xIR, 16xAF, No AA & Virtual XFB. Perfectly playable in all areas despite moderate stuttering after loading a save & when exiting water (Shader Compilation?).|tester=SolidStateDork}}
{{testing/end}}
{{testing/end}}


== Gameplay Videos ==
== Gameplay Videos ==
{{YouTube|bNsglEfBotE|Metroid Prime Trilogy (MP1 & MP2) HD Gameplay|br}}
{{VideoGallery
 
|vid1=Jf27he-pHwQ|cap1=Metroid Prime 1 Dolphin 5.0 vs Wii Comparison - The Retro Byte
{{Navigation Metroid}}
|vid2=bNsglEfBotE|cap2=Metroid Prime Trilogy (MP1 & MP2) HD Gameplay
|vid3=rBlDZz1_D2Y|cap3=Metroid Prime: Trilogy - Dolphin Emulator 5.0-12656 [1080p HD] - Nintendo Wii
}}
{{Navigation/Metroid}}


[[Category:Wii games]]
[[Category:Wii games]]
Retrieved from "https://wiki.dolphin-emu.org/index.php?title=Special:MobileDiff/75078...175581"

Navigation menu