Metroid Prime (GC): Difference between revisions

{{Infobox VG

|image    = [[File:Metroid_prime_box_art.jpg|300px]]

|developer = Retro Studios

|publisher = Nintendo

|released  = {{vgrelease|NA=November 17, 2002}}{{vgrelease|JP=February 28, 2003|EU=March 21, 2003|AUS=April 3, 2003}}

|genre    = First-person action-adventure, First-person shooter, Action-adventure

An updated version exists for the [[Wii]] as part of the [[Metroid Prime: Trilogy]]; which also contains the sequels [[Metroid Prime 2: Echoes]] and [[Metroid Prime 3: Corruption]].

== Problems ==

== Configuration ==

<!--A full list of options is available at Template:Config/doc-->

{{Config

}}

{{VersionCompatibilityVersion|3.0-697|***|aram-dma merger causes sound to stop even with LLE}}

{{VersionCompatibilityVersion|3.0-766|***|aram-dma reverted, but microstuttering worsened by a prior revision}}

{{VersionCompatibilityVersion|4.0-5124|****|Refraction Slowdown fixed}}

{{VersionCompatibilityClose}}

{{testing/entry|revision=3.0-201|OS=Windows 7|CPU=Intel Core i5-760 @ 2.8GHz|GPU=ATI Radeon HD 5850|result=DX9, 2x IR, 4xAA, and running very smooth. Haven't noticed any negative effects from Cache Display Lists. XAudio2 distorted various sounds, using DSound instead.|tester=Maave}}

{{testing/entry|revision=3.0-201|OS=Windows 7|CPU=Intel Core i7-2620M @ 2.7GHz|GPU=Intel HD 3000|result=Using recommended settings and dx9 back-end. Its playable, with a consistent 30FPS, however it will glitch only in certain rooms, and sometimes in morph ball form it will drop to 11FPS. Some audio issues but for the most part very good and consistent. Also playing in 720p and frame set to auto instead of native.|tester=cohn}}

{{testing/entry|revision=3.0-586|OS=Windows 7|CPU=AMD Athlon II X4 640 @ 3GHz|GPU=ATI Radeon HD 4200|result=With recommended settings works almost flawlessly. Lava, water, and snow sometimes lowers the FPS, but the FPS will go right back up if you turn the visor to scan mode. IMPORTANT: I don't know about other revisions, but save states are broken; loading a state results in a black screen.|tester=}}

{{testing/entry|revision=3.0-631|OS=Windows 7|CPU=Intel Core i7-920 @ 3.7GHz|GPU=AMD Radeon HD 6950|result=Absolutely fluid FPS even with 2.5x native on HLE audio, however, massive audio glitches occur (cracking, noise and 90% of sounds are wrong), LLE audio fixes this but yields a comparatively pathetic performance, even on 1x native with settings trimmed on extreme performance very annoying lags occur in fights with more than 2 opponents. LLE on a discrete thread seems to improve this a bit, but not satisfyingly. High FPS drops in large outside areas when water drops come onto the visor. UPDATE: I have recently found the solution: Enabling "Accurate VBeam emulation" causes a slight lag and FPS-drop in the menu and just after entering new areas, but increases overall performance substantially and makes it well playable.|tester=}}   

{{testing/entry|revision=4.0-4478|OS=Windows 8|CPU=Intel Core i7-3520M @ 3.3GHz|GPU=NVIDIA GeForce GT 640M LE|result= Played with D3D, 1.5x resolution. Near perfect, slows down only in very large areas or when splashing in water for some reason. FPS is constantly at around 60, VPS is stable as well. Micro-stuttering still an issue but barely noticeable; the sound is fantastic with the HLE engine, not a single error. I managed to complete the game with minor problems; the x-ray and thermal visors failed to work once for some reason, but worked again after resetting the emulator. It crashed four times in total, always in the same situation; when entering rooms where purple energy enemies are found, those that can only be killed via wave beam, the game randomly crashed. In other cases a FIFO overflow error occurred, although it didn't stop the emulation or crash the game. This is very close to perfect, and my computer is nowhere near powerful for Dolphin. Modifications to the JIT and FIFO have made a huge difference.|tester=UDEM42}}

{{testing/entry|revision=4.0-5347|OS=Windows 7|CPU=Intel Core i7-4770K @ 4.2GHz|GPU=NVIDIA GeForce GTX 660 Ti|result=Played through the pirate frigate section, it seems perfect and running at full speed. Using D3D, auto rescaling at 1920x1080, 2xAA 4xAF, other settings at defaults. The microstuttering is there but isn't really a problem. It was present at places like the pan over the frigate during the opening cutscene and using the morph ball for the first time. Each pause was 150ms or so. Repeating these actions did not result in stuttering since the shaders were cached.|tester=ThatBum}}

{{testing/entry|revision=5.0-rc-34|OS=Windows 10|CPU=Intel Core i5-6600K @ 4.5GHz|GPU=NVIDIA GeForce GTX 970|result='''Final Verdict''': At the expense of the unfortunate stuttering and slowdown issues (varying from mostly minor, to sudden Matrix-inducing moments), Metroid Prime looks absolutely stunning in Dolphin, running in 1080p widescreen at a mostly consistent 60FPS. What's more, there are no stretching artifacts or culling issues involved. Used Gamecube Controller, with Mayflash Adapter, and installed the Gamecube drivers via the [https://wiki.dolphin-emu.org/index.php?title=How_to_use_the_Official_GameCube_Controller_Adapter_for_Wii_U_in_Dolphin Dolphin wiki itself].

Settings: Backend OpenGL (Direct3D seems to deliver similar performance), Enable Cheats (true), Force 16:9, V-Sync (true), 3x Native (1920x1584), 4xAA (4x SSAA is possible, but tends to cause more stuttering? it's difficult to say), Per-Pixel Lighting (true), Widescreen Hack (true) (don't forget to enable cheats or the following AR Code). AR Code Disable Culling (aka Widescreen Hack fix): 043451D0 38600001  043451D4 4E800020. Thanks to the community for the code. This fixes an issue where most objects that are outside of the original 4:3 FoV would turn invisible to try and save on graphical resources (a technique called Culling). This AR code is essential for Dolphin VR. Keep in mind certain visual effects still render incorrectly in a 4:3 aspect ratio, such as the "Colour Correction" effect when Samus is underwater. You might also wish to disable the HUD and Helmet view within the game's Options. For a true native experience, set the aspect ratio to 4:3, disable Widescreen Hack, and disable the AR Code.

All other settings left to default. It's hard to say if there's a performance difference with reduced/increased settings due to the micro stuttering issue that occurs regardless of settings. On a side note, Dolphin VR 4.0-9170-dirty with Oculus Rift DK2 and SDK 0.7 works well, drawback being choppy headtracking. With OpCode Replay Settings: Pullup 60FPS to 75FPS (true), and Disable Opcode Warnings (true), headtracking is smooth but geography will flash everywhere making the game quickly unplayable.|tester=PyroPaperPlanes}}

{{testing/end}}

== Gameplay Videos ==

{{VideoGallery

}}

[[Category:GameCube games]]