Metroid Prime (GC): Difference between revisions

Metroid Prime (GC) (view source)

Revision as of 22:14, 1 December 2014

No change in size , 1 December 2014

no edit summary

Madamunkey

2

edits

@@ Line 76: / Line 76: @@
 {{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-4199|OS=Windows Vista x64|CPU=Intel Core Pentium D @ 3.2GHz|GPU=ATI Radeon HD 5800|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/end}}