TimeSplitters 2: Difference between revisions

m
→‎Testing: General maintenance with AutoWikiBrowser in Bot mode
m (→‎top: General maintenance with AutoWikiBrowser in Bot mode)
m (→‎Testing: General maintenance with AutoWikiBrowser in Bot mode)
 
Line 120: Line 120:
{{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=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.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=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.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/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}}