Goat Simulator 3 (PPSA04158)

[JJenkx]

Existing thread

• I searched this category for the title ID and no thread exists for this title on any platform.

Title

Goat Simulator 3 (PPSA04158)

Content version tested

01.000.000

AnyPS5 commit

main 83462cc with #9628 (relinker and libraries from that build), Release, WinLibs GCC 15.2.0 UCRT. Runs were launched through the shared queue with APS5_PLAYGO_UNLISTED_CHUNKS=installed and scripted controller input (APS5_PAD_INPUT_FILE with tools/pad_input.py: cross every 10 s from 40 s).

System tested

Windows 11 Enterprise 10.0.22621, Ryzen 9 5950X, Radeon RX 6700 XT (AMD proprietary driver).

Static notes

• Engine: Unreal Engine 4. ue4commandline.txt is ../../../Goat2/Goat2.uproject, and the content is one goat2-ps5.pak.
• Movies: all ten goat2/content/movies/*.mp4 are H.264 video with AAC audio.
• PlayGo: the dump has no playgo-chunk.dat or playgo-scenario.json, so the runs use APS5_PLAYGO_UNLISTED_CHUNKS=installed.
• Imports: the audit with these libraries reports 2,679 unique imports, none absent, and 15 stubs. The stubs are the libSceJobManager AGC workload calls (sceAgcAcbSetWorkloadStreamInactive, sceAgcAcbSetWorkloadComplete, sceAgcAcbSetWorkloadsActive, sceAgcUpdateInterpolantMapping_0100 and others).

Furthest point

In-game. With cross pressed every 10 s, the title passes the photosensitive-seizure warning (35 s) and reaches the main menu and World Saves (60 s). It then starts a new save and shows the in-game loading screen (150–240 s). The in-engine intro cinematic follows (360 s, "Coffee Stain North" credit with a "△ Skip" prompt), and by 590 s the cinematic has ended in controllable gameplay: the HUD shows the first quest ("Goat Castle — Enter your home"), the compass and the movement tutorial ("L Move character / R Turn"). Nothing stopped, crashed or reported an unimplemented call in 600 s.

What is shown

• Menus: the warning, title and save menus render correctly, at about 8 fps.
• 3D scenes: geometry, camera and animation are right, but the image is almost black and white. The sky renders either black (480 s) or blown out to white (590 s), there is barely any colour, and shadowed surfaces crush to solid black. This looks like a broken exposure or tone-mapping (post-process) pass, not missing geometry.
• Frame rate: about 8 fps in menus, under 1 fps during the world load and about 3 fps in gameplay. tools/trace_digest.py puts the time in Driver.Packet on one worker at 99 % busy, so the menus are CPU-bound in command-packet processing. The GPU is busy about 90 ms per present.

Current blocker

No hard blocker. Two open problems:

1. The 3D image's exposure and tone mapping (near-monochrome, crushed shadows, sky black or blown out).
2. Performance: about 8 fps in menus, with Driver.Packet the largest phase.

A run that presses △ to skip the intro is queued, to reach gameplay sooner and test stick movement.