Repository navigation
LEGO® Builder's Journey (PPSA05496) #7926
whamre
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.
Uh oh!
There was an error while loading. Please reload this page.
mainf6eeca4 plus the PRs below--windows --module-dir Media/Modules --module-dir Media/Plugins. eboot,sce_moduleand the Unity plugins unwrapped from SELF withtools/unwrap_self.pyStatus
With the PRs below applied, it boots, plays the LEGO logo and reaches the first playable scene at about 7 FPS (frame p50 ≈ 145 ms). It hasn't been played beyond that scene yet.
Stops on
main, in the order they're hitresumeEvent; the render thread then waits on the main thread).depth mips (DB_DEPTH_VIEW MIP_LEVEL) is unsupported (register 0x2 = 0x04000000)right after the logo: depth is rendered into mip 1 of a 64 KiB Z_X chain, without HTILE.Performance notes
APS5_TEXTURE_CACHE_MIB=3600.agc_compute_pipeline_replay), so the first visit after the logo stalls for 2–3.5 minutes until the driver cache holds them.APS5_SPANNED_WAVE=1didn't help: the largest modules stay two-lane, and steady state is unchanged.Imports that can still throw (from the relinker registry)
sceNpTrophy2GetRewardIcon(PSNCore.prx),sceAgcAcbSetFlip,sceAgcUpdateInterpolantMapping_0100, and the AgcDriver capture Start/Stop/Trigger calls (via libSceJobManager). Partial:sceAgcAcbSetWorkload*,sceAjmInstanceCreate,sceAjmBatchStart/sceAjmBatchJob*,sceSystemServiceLoadExec. None of these were hit before the first scene.Stack tried
mainf6eeca4 + #7652 (an equivalent local change) + #7927 + #7873 (hang-dump stack candidates, used to find stop 1) + the storage budget change above.AI-assisted: yes. The runs and numbers are from my machine.
All reactions