Castlevania Judgment: Difference between revisions

m
Text replacement - "Core i5 3570K" to "Intel Core i5-3570K @ 3.4GHz"
m (Text replacement - "Core i5 3570K" to "Intel Core i5-3570K @ 3.4GHz")
Line 44: Line 44:
{{testing/entry|revision=4.0.2|OS=Windows 7|CPU=AMD Phenom II 975 @ 4.12GHz|GPU=AMD R9 290|result=Using the D3D11 backend, Progressive scan enabled, using DSP LLE, Internal Resolution 2.5x Native (1600x1320), using Scaled EFB Copies, running in fullscreen with a resolution of 1680x1050, External Framebuffer set to Virtual, using OpenMP Texture Decoder, using both a real Wii Remote (nonfunctional) and an emulated GameCube controller, and all other settings at their defaults. Game runs at a stable 60FPS in menus, but often/regularily slows down during the intro cinematic and gameplay, downwards of ~50FPS, and the sound stutters/outright fails a lot when this occurs. |tester=incassum}}
{{testing/entry|revision=4.0.2|OS=Windows 7|CPU=AMD Phenom II 975 @ 4.12GHz|GPU=AMD R9 290|result=Using the D3D11 backend, Progressive scan enabled, using DSP LLE, Internal Resolution 2.5x Native (1600x1320), using Scaled EFB Copies, running in fullscreen with a resolution of 1680x1050, External Framebuffer set to Virtual, using OpenMP Texture Decoder, using both a real Wii Remote (nonfunctional) and an emulated GameCube controller, and all other settings at their defaults. Game runs at a stable 60FPS in menus, but often/regularily slows down during the intro cinematic and gameplay, downwards of ~50FPS, and the sound stutters/outright fails a lot when this occurs. |tester=incassum}}
{{testing/entry|revision=4.0-613|OS=Windows 7|CPU=AMD Phenom II 975 @ 4.12GHz|GPU=AMD R9 290|result=Using the D3D11 backend, Progressive scan enabled, using DSP LLE, Internal Resolution 2.5x native (1600x1320), using scaled EFB copies, running in fullscreen with a resolution of 1680x1050, External Framebuffer set to Virtual, using OpenMP Texture Decoder, disabled "Skip Format Changes", Framelimit set to 60, using both a real Wii Remote (nonfunctional) and an emulated GameCube controller, and all other settings at their defaults. Game Runs fairly stable at 30FPS throughout the intro cinematic, and mostly stable at 30FPS in-game: it only experiences slowdowns specifically when a fire effect/fire effects are in play, and even then depending on how much else is going on/how much else is in effect on-screen. It seems to be specifically the fire-type effects (the red beam/stage hazard in the cathedral stage, certain characters attacks etcetera) that slows the game down. Further, the sound stutters during certain cutscenes and "ultimate" attacks. The most glaring bug is that one of the characters ("Aeon") Charge attack is supposed to turn the screen completely white for a few seconds before returning to normal at the end of the animation ; however, instead the white layer stays on the screen for the entire duration of the attack (a few seconds longer than the actual animation the character performs), making it impossible to use the attack; you can still hear sound and the game responds to input, so the emulation is fine, and once the effect of the attack is over, the white layer disappears and the game returns to normal. However, performance-wise, this is a significant improvement from revision 4.0.2.|tester=incassum}}
{{testing/entry|revision=4.0-613|OS=Windows 7|CPU=AMD Phenom II 975 @ 4.12GHz|GPU=AMD R9 290|result=Using the D3D11 backend, Progressive scan enabled, using DSP LLE, Internal Resolution 2.5x native (1600x1320), using scaled EFB copies, running in fullscreen with a resolution of 1680x1050, External Framebuffer set to Virtual, using OpenMP Texture Decoder, disabled "Skip Format Changes", Framelimit set to 60, using both a real Wii Remote (nonfunctional) and an emulated GameCube controller, and all other settings at their defaults. Game Runs fairly stable at 30FPS throughout the intro cinematic, and mostly stable at 30FPS in-game: it only experiences slowdowns specifically when a fire effect/fire effects are in play, and even then depending on how much else is going on/how much else is in effect on-screen. It seems to be specifically the fire-type effects (the red beam/stage hazard in the cathedral stage, certain characters attacks etcetera) that slows the game down. Further, the sound stutters during certain cutscenes and "ultimate" attacks. The most glaring bug is that one of the characters ("Aeon") Charge attack is supposed to turn the screen completely white for a few seconds before returning to normal at the end of the animation ; however, instead the white layer stays on the screen for the entire duration of the attack (a few seconds longer than the actual animation the character performs), making it impossible to use the attack; you can still hear sound and the game responds to input, so the emulation is fine, and once the effect of the attack is over, the white layer disappears and the game returns to normal. However, performance-wise, this is a significant improvement from revision 4.0.2.|tester=incassum}}
{{testing/entry|revision=4.0-8143|OS=Windows 7|CPU=Core i5 3570K|GPU=NVIDIA GTX 760|result=Perfect.  100%'d the game because of the report of that attack causing broken graphics.  I got to see every little thing about this game.  It plays perfectly in Dolphin.  Some slight shader generation stuttering, but, that's not really a bug.|tester=JMC47}}
{{testing/entry|revision=4.0-8143|OS=Windows 7|CPU=Intel Core i5-3570K @ 3.4GHz|GPU=NVIDIA GTX 760|result=Perfect.  100%'d the game because of the report of that attack causing broken graphics.  I got to see every little thing about this game.  It plays perfectly in Dolphin.  Some slight shader generation stuttering, but, that's not really a bug.|tester=JMC47}}
{{testing/end}}
{{testing/end}}