Metroid Prime (GC): Difference between revisions

Jump to navigation Jump to search
→‎Testing: new entry
No edit summary
(→‎Testing: new entry)
Line 136: Line 136:
{{testing/entry|revision=5.0|OS=Windows 10|CPU=AMD A4 7210|GPU=AMD Radeon R5 Graphics|result=Good but a little choppy.|tester=Dogmander25}}
{{testing/entry|revision=5.0|OS=Windows 10|CPU=AMD A4 7210|GPU=AMD Radeon R5 Graphics|result=Good but a little choppy.|tester=Dogmander25}}
{{testing/entry|revision=5.0-129|OS=Windows 10|CPU=Intel Core i3-6320|GPU=NVIDIA GeForce GTX 750 TI|result=Works great even on moderate hardware. Black bar problem is gone and shader stutter wasn't as bad as i remember but I did have a brief moment of lag right after the opening cut-scene. I only did the intro so far but I am impressed by how much better this game runs!|tester=IceStrike256}}
{{testing/entry|revision=5.0-129|OS=Windows 10|CPU=Intel Core i3-6320|GPU=NVIDIA GeForce GTX 750 TI|result=Works great even on moderate hardware. Black bar problem is gone and shader stutter wasn't as bad as i remember but I did have a brief moment of lag right after the opening cut-scene. I only did the intro so far but I am impressed by how much better this game runs!|tester=IceStrike256}}
{{testing/entry|revision=5.0-5421|OS=Windows 10|CPU=Intel Core i3-3220 @ 3.3GHz|GPU=NVIDIA GeForce GTX 1060|result=Nearly perfect with default settings (OpenGL). Most of the stuttering on a fresh shader cache is confined to the intro; afterwards, things were a lot more smooth. Hybrid ubershaders eliminates the stuttering entirely, but for me using hybrid ubershaders with OpenGL caused massive slowdown to below 50% speed when looking at the map (gameplay is fine). Direct3D11 and Vulkan with ubershaders both fix stuttering as well and keep the map at full speed.|tester=Xerxes}}
{{testing/end}}
{{testing/end}}


6,906

edits

Navigation menu