9
edits
Aplayer12345 (talk | contribs) m (Clock speed) |
|||
Line 500: | Line 500: | ||
{{testing/entry|revision=5.0-4322|OS=Windows 10|CPU=Intel Core i7-4790K @ 4GHz|GPU=NVIDIA GeForce GTX 1070|result=50 Shine run w/ Vulkan at 3xIR, 1xAF, No AA & settings recommended under "Graffiti Behaves Oddly". Smooth performance at 60FPS & 16:9 (using the codes above), no noticeable drops. Only listed problem encountered was Debug Cubes, no crashes or map slowdown.|tester=SolidStateDork}} | {{testing/entry|revision=5.0-4322|OS=Windows 10|CPU=Intel Core i7-4790K @ 4GHz|GPU=NVIDIA GeForce GTX 1070|result=50 Shine run w/ Vulkan at 3xIR, 1xAF, No AA & settings recommended under "Graffiti Behaves Oddly". Smooth performance at 60FPS & 16:9 (using the codes above), no noticeable drops. Only listed problem encountered was Debug Cubes, no crashes or map slowdown.|tester=SolidStateDork}} | ||
{{testing/entry|revision=5.0-8935|OS=Windows 10|CPU=AMD Ryzen 5 2400G @ 3.9GHz|GPU=AMD Radeon RX Vega 11 IGP|result=Configuration: 720p, 1xAF, no AA. Encounters "Failed to submit command buffer" during or straight after the opening scene with Vulkan, making it completely unplayable. Other backends run just fine with perfect speed.|tester=amiboss}} | {{testing/entry|revision=5.0-8935|OS=Windows 10|CPU=AMD Ryzen 5 2400G @ 3.9GHz|GPU=AMD Radeon RX Vega 11 IGP|result=Configuration: 720p, 1xAF, no AA. Encounters "Failed to submit command buffer" during or straight after the opening scene with Vulkan, making it completely unplayable. Other backends run just fine with perfect speed.|tester=amiboss}} | ||
{{testing/entry|revision=5.0-10922|OS=Windows 10|CPU=AMD Ryzen 7 3700X @ 4. | {{testing/entry|revision=5.0-10922|OS=Windows 10|CPU=AMD Ryzen 7 3700X @ 4.2GHz|GPU=NVIDIA GeForce GTX 1060|result=OpenGL, 3xIR, 1xAF, 4x MSAA, recommended settings. With the 60 FPS and 16:9 codes, the game runs perfectly from start to finish with no noticeable drops.|tester=Aplayer12345}} | ||
{{testing/end}} | {{testing/end}} | ||
edits