City Racer: Difference between revisions

Jump to navigation Jump to search
→‎Testing: ##GHz to ## GHz mass edit
mNo edit summary
(→‎Testing: ##GHz to ## GHz mass edit)
Line 47: Line 47:
{{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=5.0-1103|OS=Windows 10|CPU=Intel Xeon E5 V3 @ 2.3GHz|GPU=NVIDIA GeForce GTX 780|result=Loading screen after intro video took a longer than expected time (~3-5 minutes). Eventually, it loaded the main menu, which was slow but responsive (10-15 FPS). Getting into a quick game was possible; the game itself ran fine at solid 60 FPS with no perceived graphical problems. The car, however, experienced some deadzone issues (might be on my end). This was through the OpenGL plugin with 4x IR, 2x MSAA, and 4x Anisotropic filtering. |tester=saintschultz}}
{{testing/entry|revision=5.0-1103|OS=Windows 10|CPU=Intel Xeon E5 V3 @ 2.3 GHz|GPU=NVIDIA GeForce GTX 780|result=Loading screen after intro video took a longer than expected time (~3-5 minutes). Eventually, it loaded the main menu, which was slow but responsive (10-15 FPS). Getting into a quick game was possible; the game itself ran fine at solid 60 FPS with no perceived graphical problems. The car, however, experienced some deadzone issues (might be on my end). This was through the OpenGL plugin with 4x IR, 2x MSAA, and 4x Anisotropic filtering. |tester=saintschultz}}
{{testing/end}}
{{testing/end}}


Navigation menu