Call of Duty: World at War - Final Fronts: Difference between revisions

Call of Duty: World at War - Final Fronts (view source)

1,160 bytes added , 11 May 2022

Test results & workaround for lag.

ninja

1

edit

@@ Line 79: / Line 79: @@
 |Comments=Europe v02.00(14/06/2004), Playable, The game barely runs at low resolution (PS2) 35-40 FPS, due to the fact that the processor is weak.
 |Tester=Chern40+7
+}}
+{{TestingEntry
+|Status=2
+|Region=NTSC-U
+|OS=Windows 10, x64
+|CPU=Intel Core i7-6700 @ 3.40GHz
+|GPU=AMD Radeon RX 480
+|Revision=v1.7.0-Nightly-2618
+<spoiler show="Settings Emulator" hide="Hide">
+* '''Speedhacks:'''
+** mVU Flag Hack: Enabled
+** Instant VU1: Enabled
+</spoiler>
+|Graphics=GSdx-AVX2
+<spoiler show="Settings" hide="Hide">
+* Renderer: Direct3D 12 (Hardware)
+* Internal Resolution: 2x Native (~720p)
+* Texture Filtering: Bilinear (PS2)
+* Anisotropic Filtering: Off
+* Mipmapping: Automatic (Default)
+* CRC Hack Level: Automatic (Default)
+* Blending Accuracy: High
+* Texture Preloading: Full(Hash Cache)
+* HW Hacks: Automatic
+</spoiler>
+|Sound=
+* SPU2-X
+* LilyPad
+|Comments=This game suffers from texture cache issues that cause massive slowdown, so at the start of each mission you must press F9 twice to swap between Software and Hardware renderers in order to clear the cache. Once that's done, the game runs flawlessly at 2x resolution with no noticeable glitches- though it's not quite fast enough to handle 3x resolution consistently. Recommend using Direct3D 12 with High Blending Accuracy for best results.
+|Tester={{ForumUser|ScaryHobbit}}
 }}
 {{TestingFooter}}