3,800
edits
Metroid Prime (Metroid Prime: Trilogy): Difference between revisions
Metroid Prime (Metroid Prime: Trilogy) (view source)
Revision as of 05:24, 28 February 2024
, 28 FebruaryGeneral maintenance with AutoWikiBrowser in Bot mode
No edit summary |
m (General maintenance with AutoWikiBrowser in Bot mode) |
||
| Line 8: | Line 8: | ||
|modes = Single-player | |modes = Single-player | ||
|input = Wii Remote + Nunchuk | |input = Wii Remote + Nunchuk | ||
|forumlink = | |forumlink = https://forums.dolphin-emu.org/Thread-wii-metroid-prime-trilogy--26043 | ||
}} | }} | ||
| Line 16: | Line 16: | ||
== Game Pages == | == Game Pages == | ||
This page should be used for specific issues with the Metroid Prime sub-game of [[Metroid Prime: Trilogy]]. | 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 56: | Line 56: | ||
=== Dot in IR>1 === | === Dot in IR>1 === | ||
<!-- Shared problem with other [[Metroid Prime: Trilogy]] games --> | <!-- 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. | 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. | ||
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. | 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. | ||
| Line 83: | Line 83: | ||
{{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|CPU=Intel Core i5-2500K @ 4.4 GHz|GPU=NVIDIA GeForce GTS 250|result=Close to perfect | {{testing/entry|revision=7689|OS=Windows 7|CPU=Intel Core i5-2500K @ 4.4 GHz|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|CPU=AMD Phenom II X4 980 @ 4.2 GHz|GPU=NVIDIA GeForce 8800 GT|result=DX9, 1.5x Resolution, 4x SSAA, 8x AF runs at 90-100%. | {{testing/entry|revision=7714|OS=Windows 7|CPU=AMD Phenom II X4 980 @ 4.2 GHz|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|CPU=AMD Phenom II X6 1090T @ 3.2 GHz|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.2 GHz|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|CPU=Intel Core i7-3770K @ 4.4 GHz|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. | {{testing/entry|revision=3.0-766|OS=Windows 7|CPU=Intel Core i7-3770K @ 4.4 GHz|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|CPU=Intel Core i5-2500K @ 4.3 GHz|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=3.5-379|OS=Windows 7|CPU=Intel Core i5-2500K @ 4.3 GHz|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.6 GHz|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-2826|OS=Windows 7|CPU=Intel Core i7-4790K @ 4.6 GHz|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}} | ||
| Line 93: | Line 93: | ||
{{testing/entry|revision=5.0-1637|OS=Windows 10|CPU=Intel Core i7-4790 @ 3.6 GHz|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-1637|OS=Windows 10|CPU=Intel Core i7-4790 @ 3.6 GHz|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.8 GHz|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-1943|OS=Windows 10|CPU=Intel Core Xeon-5670 @ 4.8 GHz|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- | {{testing/entry|revision=5.0-2612|OS=Windows 8.1|CPU=Intel Core i7-5820K @ 3.8 GHz|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 @ 4 GHz|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/entry|revision=5.0-4322|OS=Windows 10|CPU=Intel Core i7-4790K @ 4 GHz|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}} | ||