Bureaucrats, ninja, Administrators
67,565
edits
Call of Duty: World at War - Final Fronts: Difference between revisions
Call of Duty: World at War - Final Fronts (view source)
Revision as of 10:25, 27 March 2024
, 27 March1 revision imported
No edit summary |
m (1 revision imported) |
||
| (37 intermediate revisions by 6 users not shown) | |||
| Line 11: | Line 11: | ||
The Game has 4 campaigns: War in the Pacific, Winter Offensive, Victory in Europe, and Victory in the Pacific. The player takes on the role of a marine in the Pacific campaigns and both British and American soldiers in the European campaign. Unlike other "World at War" titles, Final Fronts has a training level. The War in the Pacific and Victory in the Pacific Campaigns see Private Joe Miller (a reference to World at War protagonist C. Miller) and his fellow soldiers Sgt. Roebuck and Pvt. Polonsky (also in World at War) fight their way through Japanese defenses on Guadalcanal, Betio, Saipan, and Okinawa | The Game has 4 campaigns: War in the Pacific, Winter Offensive, Victory in Europe, and Victory in the Pacific. The player takes on the role of a marine in the Pacific campaigns and both British and American soldiers in the European campaign. Unlike other "World at War" titles, Final Fronts has a training level. The War in the Pacific and Victory in the Pacific Campaigns see Private Joe Miller (a reference to World at War protagonist C. Miller) and his fellow soldiers Sgt. Roebuck and Pvt. Polonsky (also in World at War) fight their way through Japanese defenses on Guadalcanal, Betio, Saipan, and Okinawa | ||
<!-- General props --> | <!-- General props --> | ||
|widescreen = 1 | |widescreen = 1 | ||
|ko_rating = 15 | |ko_rating = 15 | ||
|eu_rating = 16+ | |eu_rating = 16+ | ||
|au_rating = | |au_rating = M | ||
|au_rating_text = Violence | |||
|na_rating = T | |na_rating = T | ||
|na_rating_text = Mild Language, Violence | |na_rating_text = Mild Language, Violence | ||
| Line 37: | Line 37: | ||
|CRCsPAL = | |CRCsPAL = | ||
|releasedatePAL = November 12, 2008 <small>(Australia)</small><br />November 14, 2008<br />December 24, 2009 <small>(Platinum)</small> | |releasedatePAL = November 12, 2008 <small>(Australia)</small><br />November 14, 2008<br />December 24, 2009 <small>(Platinum)</small> | ||
|statusPAL = | |statusPAL = 2 | ||
|linuxstatusPAL = | |linuxstatusPAL = | ||
|macstatusPAL = | |macstatusPAL = | ||
| Line 67: | Line 67: | ||
}} | }} | ||
{{TestingEntry | {{TestingEntry | ||
|Status= | |Status=2 | ||
|Region=NTSC-U/PAL-M4 | |Region=NTSC-U/PAL-M4 | ||
|OS=Windows 8.1, x64 | |OS=Windows 8.1, x64 | ||
|CPU=Intel(R) Pentium(R) CPU G2030 @ 3.00GHz | |CPU=Intel(R) Pentium(R) CPU G2030 @ 3.00GHz | ||
|GPU=PALIT GeForce GT 1030 @ 2 GB | |GPU=PALIT GeForce GT 1030 @ 2 GB | ||
|Revision=v1. | |Revision=v1.4.0 | ||
|Graphics= | |Graphics=GSdx32 SSSE3 1.0.0 | ||
|Sound= | |Sound= | ||
*SPU2-X | *SPU2-X 2.0.0 | ||
*LilyPad | *LilyPad 0.11.0 | ||
|Comments= | |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 | |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 | |||
<!-- | |||
* '''Speedhacks:''' | |||
** mVU Flag Hack: Enabled | |||
** Instant VU1: Enabled | |||
--> | |||
|Graphics=GSdx-AVX2 | |||
<!-- | |||
* 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 | |||
--> | |||
|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}} | {{TestingFooter}} | ||
| Line 105: | Line 135: | ||
== | ==Fixed Issues== | ||
{{Issue | |||
|IssueName=Red bold stripes on Direct3D 9 (Hardware) rendering | |||
|IsFixed=1 | |||
|IssueLevel=0 | |||
|AffectedVersions=NTSC-U and PAL | |||
|Description=Red bold stripes appear on Direct3D 9 (Hardware) rendering during gameplay. | |||
|Workaround=Use Software mode or change the rendering to Direct3D 11 or OpenGL. | |||
}} | |||
{{Issue | {{Issue | ||
|IssueName= | |IssueName=Game freezes after checking memory card. | ||
|IsFixed= | |IsFixed=1 | ||
|IssueLevel=2 | |IssueLevel=2 | ||
|Description= | |AffectedVersions=NTSC-U and PAL (due to emulator version 1.5.0, 1.6.0 and 1.7.0) | ||
|Workaround= | |Description=Since emulator versions 1.5.0 and up to 1.7.0 dev the game freezes with TLB Miss messages. The console log shows the following: | ||
<pre> | |||
(EE pc:00425F5C) TLB Miss, addr=0x53454258 [load] | |||
(EE pc:00425F5C) TLB Miss, addr=0x534542d8 [load] | |||
(EE pc:00425FE4) TLB Miss, addr=0x53454200 [load] | |||
... | |||
</pre> | |||
|Workaround=Don't use memory cards above 8mb and use newest dev build. | |||
}} | }} | ||
{{Issue | |||
|IssueName=Ghosting in Hardware modes. | |||
|IsFixed=1 | |||
|IssueLevel=2 | |||
|Description=Ghosting and lines on the edges of the screen while in either hardware mode. | |||
|Workaround=Use Direct3D 11, enable hardware hacks and set texture offsets to X:0 and Y:800 to fix ghosting in Hardware mode. | |||
}} | |||
<!-- | |||
I cant confirm any of these issues myself right now, i only tried to make them easier to understand from the OPs. | |||
--> | |||
{{Call of Duty Franchise}} | {{Call of Duty Franchise}} | ||