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

|series    = ''Metroid'', ''Metroid Prime''

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

This game suffers from severe stuttering during shader generation. Because of the differences between how the Wii works compared to personal computers, whenever something uses the Wii's GPU, Dolphin must generate a shader to emulate it on a PC GPU. Shader generation causes a slight emulation delay while it's being created, so Dolphin caches these shaders in its shadercache folder to help keep things smooth. Most games don't care about this and play fine, but with all of the games in ''Metroid Prime Trilogy'', the shaders are so massive that they cause a significant delay, which creates a hard stutter and desyncs the GPU and CPU threads. 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. Going into new areas or showing new effects will cause the stutter and black bar, 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 stutter and desync if a new effect or region is loaded.

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 Alt-F5 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.

=== Bloom Offset ===

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

=== Visors ===

Visors will only work if EFB to Ram is enabled. Though EFB to Ram is forced by the GameINI, visor corruption may still occur if you open the graphics configuration window during gameplay. Turn on EFB to Ram in the Dolphin GUI to avoid any 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, but the dot can be removed by hiding the helmet display in the game's options (i.e. Visor, the 3rd option below Controller and Display, slide the Helmet Opacity sliders all the way to the left).

=== <s>Refraction/Lava Slowdown</s> ===

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. D3D is not affected by this problem in this game. There are also severe slowdowns with OpenGL in the Magmoor Caverns when you look down to a lava basin. Reducing the internal resolution helps a bit. It affects even strong systems. Fixed by {{revision|4.0-5124}}.

|enablespeakerdatanotes = Causes constant Wii Remote disconnects

<!--Use this template for compatibility entries: {{VersionCompatibilityVersion|revision|****}}-->

{{VersionCompatibilityVersion|7689|***}}

{{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=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=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-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.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=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 - 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 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, much like in Metroid Prime 2, otherwise constant 50FPS. Played all the way through without major glitches. Very close to being perfect.|tester=XorUnison}}

{{YouTube|bNsglEfBotE|Metroid Prime Trilogy (MP1 & MP2) HD Gameplay|br}}

 

{{Navigation Metroid}}