79,231
edits
Metroid Prime (GC): Difference between revisions
m
Text replacement - "(Core i[357]) ([^@-]+)" to "$1-$2"
m (Text replacement - "Intel i" to "Intel Core i") |
m (Text replacement - "(Core i[357]) ([^@-]+)" to "$1-$2") |
||
| Line 74: | Line 74: | ||
{{testing/entry|revision=3.5-126|OS=Windows 7 x64|CPU=Intel Core i7-2670QM @ 2.2GHz|GPU=nVidia GeForce GTX 560M|result=Running with D3D9, 1x native, 9xSSAA, EFB to Ram, Fog/Per-Pixel Depth and DSP HLE usually results in a solid 60 FPS, although significantly lower during bosses/fights with Aerotroopers, still playable though having it beat it all the way through. Audio glitches are annoying but no big deal, all I ever encountered in that regard was music disappearing randomly or when loading Save States|tester=Phazon Lord}} | {{testing/entry|revision=3.5-126|OS=Windows 7 x64|CPU=Intel Core i7-2670QM @ 2.2GHz|GPU=nVidia GeForce GTX 560M|result=Running with D3D9, 1x native, 9xSSAA, EFB to Ram, Fog/Per-Pixel Depth and DSP HLE usually results in a solid 60 FPS, although significantly lower during bosses/fights with Aerotroopers, still playable though having it beat it all the way through. Audio glitches are annoying but no big deal, all I ever encountered in that regard was music disappearing randomly or when loading Save States|tester=Phazon Lord}} | ||
{{testing/entry|revision=3.5-134|OS=Windows 8 x64|CPU=Intel Core i7-3520M @ 2.9GHz|GPU=Intel HD Graphics 4000|result=Occasional sound glitches, common for background music to drop out. After uncovering a large portion of the map, viewing it drops FPS dramatically (around 10 FPS in some cases (this is ONLY for viewing the map)). Otherwise, runs consistently at 50 FPS and 50 VPS. Very playable. I don't use the LLE recompiler because it still appears to have the same sound issues, and will also decrease FPS, I would suggest you just deal with the sound issues, and use the HLE engine.|tester=QwertyMaster}} | {{testing/entry|revision=3.5-134|OS=Windows 8 x64|CPU=Intel Core i7-3520M @ 2.9GHz|GPU=Intel HD Graphics 4000|result=Occasional sound glitches, common for background music to drop out. After uncovering a large portion of the map, viewing it drops FPS dramatically (around 10 FPS in some cases (this is ONLY for viewing the map)). Otherwise, runs consistently at 50 FPS and 50 VPS. Very playable. I don't use the LLE recompiler because it still appears to have the same sound issues, and will also decrease FPS, I would suggest you just deal with the sound issues, and use the HLE engine.|tester=QwertyMaster}} | ||
{{testing/entry|revision=3.5-380|OS=Windows 7 x64|CPU=Intel Core i7 5960X @ 4.5GHz|GPU=nVidia GeForce GTX 980|result=Perfect, no slowdowns due the great perfonmance of i7 5960x and GTX 980, but, background music still stop, please fix it|tester=AngelX}} | {{testing/entry|revision=3.5-380|OS=Windows 7 x64|CPU=Intel Core i7-5960X @ 4.5GHz|GPU=nVidia GeForce GTX 980|result=Perfect, no slowdowns due the great perfonmance of i7 5960x and GTX 980, but, background music still stop, please fix it|tester=AngelX}} | ||
{{testing/entry|revision=3.5-2215|OS=Windows 8 x64|CPU=Intel Core i7-4700HQ @ 3.2GHz|GPU=nVidia GeForce GTX 765M|result=Playable, 40-60 FPS with proper config. Sound was perfect thanks to the new DSP HLE engine.|tester=Autofire}} | {{testing/entry|revision=3.5-2215|OS=Windows 8 x64|CPU=Intel Core i7-4700HQ @ 3.2GHz|GPU=nVidia GeForce GTX 765M|result=Playable, 40-60 FPS with proper config. Sound was perfect thanks to the new DSP HLE engine.|tester=Autofire}} | ||
{{testing/entry|revision=4.0-263|OS=Windows 8 x64|CPU=Intel Core i7 3630QM @ 2.4GHz|GPU=nVidia GeForce GT 650M|result=Very Playable, 45-60 FPS, but VPS was a constant 60. Occasional loud static accompanied with cutscenes.|tester=nos770}} | {{testing/entry|revision=4.0-263|OS=Windows 8 x64|CPU=Intel Core i7-3630QM @ 2.4GHz|GPU=nVidia GeForce GT 650M|result=Very Playable, 45-60 FPS, but VPS was a constant 60. Occasional loud static accompanied with cutscenes.|tester=nos770}} | ||
{{testing/entry|revision=4.0-4199|OS=Windows Vista x64|CPU=Intel Core Pentium D @ 3.2GHz|GPU=ATI Radeon HD 3800|result=Somewhat Playable, 40-50 FPS, Particle effects and fire caused FPS to drop lower than 40, VPS was jumping from 60 to 45. Cutscenes ran mostly at 60 with exception of scenes with fire or explosions. Opening Visor and Entering Morph Ball caused short 2-3 second freeze, Levels with explorable space (such as the first) lag the most, in general, The game is playable, but not pretty.|tester=Madamunkey}} | {{testing/entry|revision=4.0-4199|OS=Windows Vista x64|CPU=Intel Core Pentium D @ 3.2GHz|GPU=ATI Radeon HD 3800|result=Somewhat Playable, 40-50 FPS, Particle effects and fire caused FPS to drop lower than 40, VPS was jumping from 60 to 45. Cutscenes ran mostly at 60 with exception of scenes with fire or explosions. Opening Visor and Entering Morph Ball caused short 2-3 second freeze, Levels with explorable space (such as the first) lag the most, in general, The game is playable, but not pretty.|tester=Madamunkey}} | ||
{{testing/entry|revision=4.0-4478|OS=Windows 8 x64|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-4478|OS=Windows 8 x64|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 x64|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=4.0-5347|OS=Windows 7 x64|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/end}} | {{testing/end}} | ||