Repository navigation
7 Days To Die - Console Edition (PPSA16645) #15991
ycbuzi
started this conversation in
Game bring-up
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Existing thread
Title
7 Days To Die - Console Edition (PPSA16645)
Content version tested
01.320.002
AnyPS5 commit
mainb11c7bf (2026-11-04), with no pull requests or local changes on top. The executable was converted by that commit's relinker on the day of the run.System tested
Windows 11 Home 10.0.26200, AMD Ryzen 9 7900 12-Core Processor, NVIDIA GeForce RTX 4070 SUPER (NVIDIA driver 616.92), Vulkan. Built myself: MinGW-w64 GCC 15.2.0 UCRT (WinLibs), Release.
Furthest point
Logos or loading screen
What is shown
The publisher logo (THE FUN PIMPS, with the pre-release notice under it) from 24 s to the end of the run, and no frame after it: AnyPS5's title counter stops at 665 frames from about 114 s on (it read 110 FPS while drawing). The title's own log (
/download0/7DaysToDie/BacktraceLogs/Player-*.log) and AnyPS5's log both end 13.3 s in, right after[DeviceGamePrefs] Applying game prefs from /app0/Media/gameprefs_PS5.xmlandApplyAllOptions streaming budget 2500 MB; nothing is logged after that, and the process keeps running. Nonot implemented, crash or driver failure line.Current blocker
A hang 13 s in, right after the title applies its options; I have not found what it waits on.
How it was run
Launched by my test pipeline right after relinking; the run ends three minutes after the first frame once 600 frames are drawn (20 minutes at most). Environment: none; no trace or profiling switches. AnyPS5's window title read 110.38 FPS with 665 frames drawn at the end; the first frame came after 3 s. The run, the screenshot check and this write-up were done with AI assistance (Claude Code); the facts are from the run's own log and window.
All reactions