God of War II

God of War II is the second game described in the author’s PS2 Web Recomp README. The documented result moves through menus and cutscenes into combat. The author says it used the same porting scripts as Gran Turismo 4 and required generic fixes rather than game-specific code.

This is project author documentation, reviewed at the listed source commit. Our community has not independently built or played the game. The reviewed README does not supply a separate God of War II recording link, so this page links to the written source instead of presenting the Gran Turismo 4 video as evidence for another game.

What has been reported

The author reports 60 frames per second in heavy combat at native internal resolution in Chrome. At twice native resolution, the reported range is 48–60 fps, attributed to the laptop’s integrated GPU limit.

Available conditions are limited:

The reviewed source establishes combat demonstrated, not a verified full playthrough. It does not establish the state of every boss, puzzle, later area, or save sequence. There is no community-tested completion claim here.

Development bugs that the author says were fixed

The README explains several failures encountered while bringing the game up:

• Missing I/O-processor timer behavior initially prevented the sound driver from producing audio.
• A recompiler boundary bug mishandled a branch delay slot, leading to corrupted memory and a crash before gameplay.
• Vector-unit clip flags became visible one instruction too late, producing large polygons that should have been culled.
• Additional generic support was needed for boot behavior, loading a module from memory, and scratchpad DMA destination chains.

Those are documented development history. The author describes fixes that allowed combat to run; these are not confirmed current bugs at the reviewed commit. If you see a similar symptom now, provide a fresh reproduction and the commit you used. A similar-looking polygon does not prove the same underlying fault has returned.

Build and record your own evidence

Use Getting Started with your own game image. The author’s approximate three-and-a-half-minute porting time used an eight-core laptop; it is an anecdote about the build workflow, not a build-time promise or the hardware specification for the browser frame-rate result.

For a useful test, name the encounter, time how long you played, and report the selected internal resolution. Include browser and driver details, the exact game release, controller behavior, and any console log. Start with 1× before comparing higher resolutions; the graphics guide explains the distinction.

Export a memory-card backup before changing your setup. If the game fails before combat, the troubleshooting checklist helps separate browser prerequisites from runtime gaps.

Use the browser check to identify missing browser features before building locally. To compare the other documented milestone, read the Gran Turismo 4 race record.