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

From PCSX2 Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 128: Line 128:
|Workaround=Use Software mode or change the rendering to Direct3D 11 or OpenGL.
|Workaround=Use Software mode or change the rendering to Direct3D 11 or OpenGL.
}}
}}
==The gallery==
<gallery widths="175px" heights="100px">
Call_of_Duty_World at War Final Fronts-chern40+7.jpg|v1.4.0, Native Resolution (PS2)
Call_of_Duty_World at War Final Fronts-chern40+7.jpg|v1.4.0, Native Resolution (PS2)
</gallery>





Revision as of 17:04, 4 November 2021

Call of Duty: World at War - Final Fronts

PAL cover
Game general and emulation properties:
ESRB rating: T (Mild Language, Violence)
PEGI rating: 16+
OFLC rating: MA
GRB rating: 15
Widescreen supported natively
CPU intensive game
Languages supported:
English: SLES-55367 & SLUS-21746
German: SLES-55369
French: SLES-55367 & SLUS-21746
Spanish: SLES-55367
Italian: SLES-55367
Region NTSC-U:
Serial numbers: SLUS-21746
Release date: November 10, 2008
CRCs: BFF3DBCB
Windows Status: Playable
Linux Status: ?
Mac Status: ?
Region PAL:
Serial numbers: SLES-55367
SLES-55369
SLES-55367/P (Platinum)
Release date: November 12, 2008 (Australia)
November 14, 2008
December 24, 2009 (Platinum)
Windows Status: Playable
Linux Status: ?
Mac Status: ?
Region NTSC-J/C/K:
Serial numbers: SLKA-25449 (Korea)
Release date: November 21, 2008 (Korea)
Windows Status: ?
Linux Status: ?
Mac Status: ?

Developer(s): Rebellion
Publisher(s): Activision
Genre: Action, Shooter, Arcade
Wikipedia: Link
Game review links: IGN4.5/10, Metacritic54/100
Game description: Developed exclusively for the PlayStation 2 computer entertainment system, this game offers a companion experience to Call of Duty: World at War, featuring its own unique set of missions, engagements and challenges that are set within the Pacific and European campaigns through many of the pivotal battles that led to the end of the world's greatest war.
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


Test configurations on Windows:


Environment Configurations Comments Tester
Region OS CPU/GPU Revision Graphics Sound/Pad
NTSC-U Windows
  • Intel Core i7 @ 3.40 GHz
  • NVIDIA GeForce GTX 285 @ 768 MB
1.1.0 (r5576) GSdx SSE41 (r5570)
  • SPU2-X 2.0.0 (2013-02-24)
  • LilyPad 0.11.0 (2013-01-13)
Runs at full speed.
NTSC-U/PAL-M4 Windows 8.1, x64
  • Intel(R) Pentium(R) CPU G2030 @ 3.00GHz
  • PALIT GeForce GT 1030 @ 2 GB
v1.4.0 GSdx32 SSSE3 1.0.0
  • SPU2-X 2.0.0
  • LilyPad 0.11.0
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. Chern40+7



Trivia

  • Original names: 콜 오브 듀티: 월드 앳 워 (SLKA-25449)


Known Issues

TLB Miss

  • Status: Active
  • Type: Major
  • Affected Game Versions: NTSC-U and PAL (due to emulator version 1.5.0, 1.6.0 and 1.7.0)
  • Description: In newer versions of the emulator, there is TLB Miss problem, after starting the game, the memory card is checked and the game freezes. The console log shows the following:
(EE pc:00425F5C) TLB Miss, addr=0x53454258 [load]
(EE pc:00425F5C) TLB Miss, addr=0x534542d8 [load]
(EE pc:00425FE4) TLB Miss, addr=0x53454200 [load]
...
  • Workaround: Use older versions of the emulator like 1.4.0 or others.

Red bold stripes on Direct3D 9 (Hardware) rendering

  • Status: Active
  • Type: Serious
  • Affected Game Versions: 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.


Public compatibility forum links