Paper Mario: The Thousand-Year Door: Difference between revisions

Line 138: Line 138:
{{testing/entry|revision=4.0-2109|OS=Windows 7|CPU=AMD FX-4300 @ 4GHz|GPU=AMD Radeon R7 260x|result=Very Playable. Constant 60FPS with all enhancements maxed. No problems using HLE.|tester=Period}}
{{testing/entry|revision=4.0-2109|OS=Windows 7|CPU=AMD FX-4300 @ 4GHz|GPU=AMD Radeon R7 260x|result=Very Playable. Constant 60FPS with all enhancements maxed. No problems using HLE.|tester=Period}}
{{testing/entry|revision=4.0-4149|OS=Windows 7|CPU=AMD Phenom II x4 965 BE @ 3.4GHz|GPU=NVIDIA GeForce GTX 660|result=Playable. FPS drops to 50% when using Paper Mode and as well when the Boo Hoos enter invisible mode.|tester=Kenny}}
{{testing/entry|revision=4.0-4149|OS=Windows 7|CPU=AMD Phenom II x4 965 BE @ 3.4GHz|GPU=NVIDIA GeForce GTX 660|result=Playable. FPS drops to 50% when using Paper Mode and as well when the Boo Hoos enter invisible mode.|tester=Kenny}}
{{testing/entry|revision=4.0-5124|OS=Mac OS X 10.9.2|CPU=Intel Core i5 @ 1.4GHz|GPU=Intel HD Graphics 5000|result=Game runs near perfect, mostly at 60FPS however does slow down when using paper abilities. A couple of minor graphics errors throughout the game. However, game is not completable as it hangs indefinitely on the final boss fight.|tester=SirSpanky}}
{{testing/entry|revision=4.0-5839|OS=Windows 10 Preview|CPU=AMD Athlon II X4 650 @ 3.2GHz|GPU=ATI Radeon HD 4200|result=Game runs perfect at a constant 60FPS at all times using the Direct3D renderer. Using the OpenGL renderer causes a significant slowdown and is not recommended. No graphical errors at all on either graphics renderer.|tester=Byteandahalf}}
{{testing/entry|revision=4.0-5839|OS=Windows 10 Preview|CPU=AMD Athlon II X4 650 @ 3.2GHz|GPU=ATI Radeon HD 4200|result=Game runs perfect at a constant 60FPS at all times using the Direct3D renderer. Using the OpenGL renderer causes a significant slowdown and is not recommended. No graphical errors at all on either graphics renderer.|tester=Byteandahalf}}
{{testing/entry|revision=4.0-5124|OS=Mac OS X 10.9.2|CPU=Intel Core i5 @ 1.4GHz|GPU=Intel HD Graphics 5000|result=Game runs near perfect, mostly at 60FPS however does slow down when using paper abilities. A couple of minor graphics errors throughout the game. However, game is not completable as it hangs indefinitely on the final boss fight.|tester=SirSpanky}}
{{testing/entry|revision=4.0-6153|OS=Windows 8|CPU=Intel Core i7 @ 4GHz|GPU=NVIDIA GeForce GTX 970|result=Using Direct3D, game runs smoothly throughout, minor (non-consistent) glitches in paper transitions, small FPS drop during bridge over Petalburg river appearance. OpenGL NOT recommended.|tester=Canopenerdude}}
{{testing/entry|revision=4.0-6153|OS=Windows 8|CPU=Intel Core i7 @ 4GHz|GPU=NVIDIA GeForce GTX 970|result=Using Direct3D, game runs smoothly throughout, minor (non-consistent) glitches in paper transitions, small FPS drop during bridge over Petalburg river appearance. OpenGL NOT recommended.|tester=Canopenerdude}}
{{testing/entry|revision=4.0-6454|OS=Windows 8.1|CPU=AMD FX-8350 @ 4.04GHz|GPU=AMD Radeon HD 5870|result=Game nearly unplayable. Game runs at 60FPS @ 4x resolution, but lags down to 10 FPS on all backends/resolutions during transition scenes (Boat at the start flipping, going through pipes, ect.) Issue not present in {{revision|4.0-3610}}.|tester=Darklords}}
{{testing/entry|revision=4.0-6454|OS=Windows 8.1|CPU=AMD FX-8350 @ 4.04GHz|GPU=AMD Radeon HD 5870|result=Game nearly unplayable. Game runs at 60FPS @ 4x resolution, but lags down to 10 FPS on all backends/resolutions during transition scenes (Boat at the start flipping, going through pipes, ect.) Issue not present in {{revision|4.0-3610}}.|tester=Darklords}}