TimeSplitters 2: Difference between revisions

m
→‎Testing: General maintenance with AutoWikiBrowser in Bot mode
(New score for less lines for AR.)
m (→‎Testing: General maintenance with AutoWikiBrowser in Bot mode)
 
(2 intermediate revisions by 2 users not shown)
Line 8: Line 8:
|modes    = Single-player, Multiplayer (4), Co-op (4), Online (16)
|modes    = Single-player, Multiplayer (4), Co-op (4), Online (16)
|input    = GameCube Controller
|input    = GameCube Controller
|forumlink = http://forums.dolphin-emu.org/Thread-gc-timesplitters-2--25980
|forumlink = https://forums.dolphin-emu.org/Thread-gc-timesplitters-2--25980
}}
}}


Line 111: Line 111:
{{testing/entry|revision=7480|OS=Ubuntu 10.04|CPU=Intel Core 2 Duo E8400|GPU=ATI Radeon HD 4850|result=Doesn't start, Unknown pointer 0xa6bd6d20|tester=Dark Fread}}
{{testing/entry|revision=7480|OS=Ubuntu 10.04|CPU=Intel Core 2 Duo E8400|GPU=ATI Radeon HD 4850|result=Doesn't start, Unknown pointer 0xa6bd6d20|tester=Dark Fread}}
{{testing/entry|revision=7480|OS=Ubuntu 10.10|CPU=Intel Pentium E5200|GPU=NVIDIA GeForce 9300|result=Works with almost 100% speed and no major graphical glitches|tester=Matthew T.}}
{{testing/entry|revision=7480|OS=Ubuntu 10.10|CPU=Intel Pentium E5200|GPU=NVIDIA GeForce 9300|result=Works with almost 100% speed and no major graphical glitches|tester=Matthew T.}}
{{testing/entry|revision=7564|OS=Windows 7|CPU=Intel Core i7-950 @ 3.07GHz|GPU=ATI Radeon HD 5770|result=Some slowness, attempting to skip the ending cinematic crashes the emulator but ran fine otherwise. For some reason though, the freeze/restart timer AR codes do not work on Dolphin whereas they work on my actual GC. There might be something wrong with that, but I can imagine, being as it's a cheat, fixing the code interpreter is low priority.|tester=Schala}}
{{testing/entry|revision=7564|OS=Windows 7|CPU=Intel Core i7-950 @ 3.07 GHz|GPU=ATI Radeon HD 5770|result=Some slowness, attempting to skip the ending cinematic crashes the emulator but ran fine otherwise. For some reason though, the freeze/restart timer AR codes do not work on Dolphin whereas they work on my actual GC. There might be something wrong with that, but I can imagine, being as it's a cheat, fixing the code interpreter is low priority.|tester=Schala}}
{{testing/entry|revision=7719|OS=Windows 7|CPU=Intel Core i7-920 @ 3.6GHz|GPU=NVIDIA GeForce GTX 560 Ti|result=Mostly runs ok, some major graphical issues outdoors on the Mexican Mission DM map (wildly flickering random colors)|tester=Adambean}}
{{testing/entry|revision=7719|OS=Windows 7|CPU=Intel Core i7-920 @ 3.6 GHz|GPU=NVIDIA GeForce GTX 560 Ti|result=Mostly runs ok, some major graphical issues outdoors on the Mexican Mission DM map (wildly flickering random colors)|tester=Adambean}}
{{testing/entry|revision=3.0-332|OS=Mac OS X 10.7.2|CPU=Intel Core i5-2435M @ 2.4GHz|GPU=Intel HD Graphics 3000|result=Crashed after creating initial profile in game.|tester=jedivulcan}}
{{testing/entry|revision=3.0-332|OS=Mac OS X 10.7.2|CPU=Intel Core i5-2435M @ 2.4 GHz|GPU=Intel HD Graphics 3000|result=Crashed after creating initial profile in game.|tester=jedivulcan}}
<!-- the report above doesn't line up with the others or the video, and the glitches shown match those of the aborted tex-cache rewrite build -->
<!-- the report above doesn't line up with the others or the video, and the glitches shown match those of the aborted tex-cache rewrite build -->
{{testing/entry|revision=3.0-373|OS=Mac OS X 10.7.2|CPU=Intel Core i7-2675QM @ 2.2GHz|GPU=AMD Radeon HD 6750M|result=Crashes before the loading screen when attempting to play single player. Says GPU is desynced. When unchecking dual-core option, game loads and crashes when the player fires a weapon. Higher framerate 25-45FPS.|tester=jedivulcan}}
{{testing/entry|revision=3.0-373|OS=Mac OS X 10.7.2|CPU=Intel Core i7-2675QM @ 2.2 GHz|GPU=AMD Radeon HD 6750M|result=Crashes before the loading screen when attempting to play single player. Says GPU is desynced. When unchecking dual-core option, game loads and crashes when the player fires a weapon. Higher framerate 25-45FPS.|tester=jedivulcan}}
{{testing/entry|revision=3.0-373|OS=Mac OS X 10.7.2|CPU=Intel Core i7-2675QM @ 2.2GHz|GPU=Intel HD Graphics 3000|result=Surprisingly gets a bit further and loads the level (vs. using the AMD Radeon HD 6750M on the same machine. GPU desync and crash occur after game loads. Game crashes still if dual-core option is turned off although the game loads to the first level ~30FPS with rapid drops. Vsync on (with dual/single core options).|tester=jedivulcan}}
{{testing/entry|revision=3.0-373|OS=Mac OS X 10.7.2|CPU=Intel Core i7-2675QM @ 2.2 GHz|GPU=Intel HD Graphics 3000|result=Surprisingly gets a bit further and loads the level (vs. using the AMD Radeon HD 6750M on the same machine. GPU desync and crash occur after game loads. Game crashes still if dual-core option is turned off although the game loads to the first level ~30FPS with rapid drops. Vsync on (with dual/single core options).|tester=jedivulcan}}
{{testing/entry|revision=3.0-416|OS=Slackware 13.37|CPU=Intel Core i5-2500K @ 3.3GHz|GPU=NVIDIA GeForce GTX 550 Ti|result=Runs at a solid 60FPS. No slowdowns or graphical glitches with OpenGL, 2x IR, 4x AA, audio throttling. Did notice a strange audio issue in the first level "Siberia", like every sound fx was trying to play one after another. Have not been able to reproduce it; HLE audio runs great. No crashes in single or multiplayer modes.|tester=Shonumi}}
{{testing/entry|revision=3.0-416|OS=Slackware 13.37|CPU=Intel Core i5-2500K @ 3.3 GHz|GPU=NVIDIA GeForce GTX 550 Ti|result=Runs at a solid 60FPS. No slowdowns or graphical glitches with OpenGL, 2x IR, 4x AA, audio throttling. Did notice a strange audio issue in the first level "Siberia", like every sound fx was trying to play one after another. Have not been able to reproduce it; HLE audio runs great. No crashes in single or multiplayer modes.|tester=Shonumi}}
{{testing/entry|revision=3.0-776|OS=Mac OS X 10.7.4|CPU=Intel Core i7 @ 2.2GHz|GPU=AMD Radeon HD 6750M|result=Not working. While trying story mode, several asserts about unknown opcodes occurred on loading screens ( "GFX FIFO: Unknown Opcode (0x6d).", also with values 0x65 or 0x5f ), however skipping them allows to progress further. First level loads fine but crashes shortly after firing/killing the first enemy (tested twice with similar results). Arcade mode crashes as soon as the first match ("Adios Amigos!") finishes loading (tested twice). Challenge mode works a bit better, I could complete "Pane in the neck" and "Bricking it" but loading the 3rd one ("Stain removal") crashed (tested once). Tested with default settings and DSP HLE.|tester=Nolendil}}
{{testing/entry|revision=3.0-776|OS=Mac OS X 10.7.4|CPU=Intel Core i7 @ 2.2 GHz|GPU=AMD Radeon HD 6750M|result=Not working. While trying story mode, several asserts about unknown opcodes occurred on loading screens ( "GFX FIFO: Unknown Opcode (0x6d).", also with values 0x65 or 0x5f ), however skipping them allows to progress further. First level loads fine but crashes shortly after firing/killing the first enemy (tested twice with similar results). Arcade mode crashes as soon as the first match ("Adios Amigos!") finishes loading (tested twice). Challenge mode works a bit better, I could complete "Pane in the neck" and "Bricking it" but loading the 3rd one ("Stain removal") crashed (tested once). Tested with default settings and DSP HLE.|tester=Nolendil}}
{{testing/entry|revision=4.0-4877|OS=Ubuntu 14.10|CPU=Intel Core i3-3220 @ 3.3GHz|GPU=NVIDIA GeForce GTX 650|result=Crashing no longer seems to be an issue. Tested the first mission in story mode and the game worked fine. On the very bottom and right sides of the screen there's a strip of pixels which is incorrectly rendered with no fix, but it's not very annoying. The health bar for one objective seemed to render strangely as well but this is very minor. Constant 100% speed and all the cutscenes and menus I went through worked perfectly.|tester=Xerxes}}
{{testing/entry|revision=4.0-4877|OS=Ubuntu 14.10|CPU=Intel Core i3-3220 @ 3.3 GHz|GPU=NVIDIA GeForce GTX 650|result=Crashing no longer seems to be an issue. Tested the first mission in story mode and the game worked fine. On the very bottom and right sides of the screen there's a strip of pixels which is incorrectly rendered with no fix, but it's not very annoying. The health bar for one objective seemed to render strangely as well but this is very minor. Constant 100% speed and all the cutscenes and menus I went through worked perfectly.|tester=Xerxes}}
{{testing/entry|revision=5.0|OS=Windows 10|CPU=Intel Core i7-4790k @ 3.5GHz|GPU=AMD R9 FURY X|result=In Direct3d 11, there were very sudden frame drops (At least in the ice mission map which was tested). OpenGL fixes this (At least for me), in the arcade custom maps I tested, everything worked great but in story mode there were graphical glitches everywhere (Mainly textures stretching) but what I tested was easily playable if the graphical hiccups are ignored. Enhancements: 3x Native, Anti-Aliasing 8x MSAA, Anisotropic Filtering 4x|tester=2haloes}}
{{testing/entry|revision=5.0|OS=Windows 10|CPU=Intel Core i7-4790K @ 3.5 GHz|GPU=AMD R9 FURY X|result=In Direct3d 11, there were very sudden frame drops (At least in the ice mission map which was tested). OpenGL fixes this (At least for me), in the arcade custom maps I tested, everything worked great but in story mode there were graphical glitches everywhere (Mainly textures stretching) but what I tested was easily playable if the graphical hiccups are ignored. Enhancements: 3x Native, Anti-Aliasing 8x MSAA, Anisotropic Filtering 4x|tester=2haloes}}
{{testing/end}}
{{testing/end}}