Cruis'n USA: Difference between revisions

Cruis'n USA (view source)

Revision as of 11:19, 29 May 2016

175 bytes added , 29 May 2016

→‎Testing

Anonymous user

2601:3C7:8300:99D0:F9CD:B0CA:7A92:FA1F

@@ Line 37: / Line 37: @@
 {{testing/entry|revision=4.0.2|OS=Windows 7|CPU=AMD FX 4130 @ 3.8GHz|GPU=AMD Radeon HD 6670|result=Slow but playable|tester=skittyz321}}
 {{testing/entry|revision=4.0-6245|OS=Windows 8.1|CPU=Intel Core i7-3630M @ 2.4GHz|GPU=NVIDIA GeForce GTX 660M|result=Accurate emulation, exhibited occasion bug when switching from Wii menu to game.|tester=akasha}}
-{{testing/entry|revision=4.0-9399|OS=Windows 7|CPU=Intel Core i5-4460 @ 3.2GHz|GPU=NVIDIA GeForce GTX 970|result=Accurate emulation. Very slow framerate in-game with default settings. A CPU Clock Override of 174% kept the framerate at a solid 30 with no noticeable side effects. I only played about 8 races in 'Cruise the USA' mode, so that gives me a pretty good idea on how the rest of the game will play out. Other settings used: 3x Native & 4x SSAA. Going any higher isn't really necessary.|tester=Jodeth}}
+{{testing/entry|revision=4.0-9399|OS=Windows 7|CPU=Intel Core i5-4460 @ 3.2GHz|GPU=NVIDIA GeForce GTX 970|result=Accurate emulation. Very slow framerate in-game with default settings. A CPU Clock Override of 175% kept the framerate at a stable 30 fps (1 player only) with no noticeable side effects. 2 player mode required an even higher override of 250% to avoid slowdown on San Francisco; the most stressful track I've encountered. No noticeable bugs at 250% either, just a shorter draw distance in 2 player mode (probably not a bug). I only played about 8 races in 'Cruise the USA' mode, so that gives me a pretty good idea on how the rest of the game will play out.|tester=Jodeth}}
 {{testing/end}}