[esatturan]

What

Adds LEGO Party! (PPSA29141, Unity 2022.3 IL2CPP, FMOD) to the tested compatibility list: it boots, reaches the menus, the studio, Challenge Zone and plays minigames. Reference-machine FPS columns are left ?; on an RTX 4070 Laptop / i7-13650HX it runs at 15–35 FPS.

Known gaps: the 4x MSAA render textures of the player portraits are skipped (empty score-panel portraits), a few depth/stencil-only draws without a pixel program are skipped, and frame rate is limited by per-draw driver CPU cost.

Tested

Windows 11, i7-13650HX, RTX 4070 Laptop: boot to gameplay with the fix PRs below applied, multi-minute runs without a crash.

Checklist

• Based on current main; no other open PR implements the same functions
• One topic per PR; follow-ups go in a new PR
• No comments in code except technical debt
• Unimplemented paths throw (NotImplemented_nid_no_patch); silent stubs are listed in TechnicalDebt
• No notes, investigation .md files or images added to the repository (attach them to this PR)
• New third-party code is a submodule built from source
• Generic behaviour, not specific to one title
• Depends on: feat(libkernel): implement _umtx_op wait and wake operations #1482 (_umtx_op), fix(libkernel): let exception delivery interrupt mutex and rwlock waits #2051, fix(ajm): decode an ATRAC9 run's whole input and follow gapless segments #2052, fix(agc): take depth fast clears from HTILE written by any kernel #2053 (with fix(agc): depth fast clears through the HTILE metadata #374), fix(libkernel): map direct memory as write-watched private pages until it is aliased #2054, fix(agc): draw stencil clears requested through DB_RENDER_CONTROL #2504, fix(agc): read buffer V#s over unreadable memory as null #2505 and fix(libSceAgcDriver): retire a depth surface once another writer covers its memory #454 (depth-surface reuse)
• AI-assisted: yes

[adriadam10]

Thanks for the data. The row says "In game, playable", but the Tested section says that needs the fix PRs below, and that isn't true of main yet:

• #1482, #2051, #2052, #2053, #2054 and #454 are still open, and #2504 and #2505 (also listed in Depends on) were closed without merging. On current main the title stops at the unresolved 04AjkP0jO9U import, as you describe in #2051.
• docs/user/COMPATIBILITY.md should describe what main does. Please hold this until the dependencies have landed, then re-check on current main and update the "Tested" section with that run (and drop #2504/#2505 from Depends on, or say what replaces them).
• #690 edits the same table (line 5), so whichever lands second will need a rebase.

[adriadam10]

Following up on the earlier review, nothing has changed on this branch and the same points apply:

• The row says "In game, playable", but the Tested section says that needs open PRs (#1482, #2051, #2053, #2054, #454); #2052, #2504 and #2505 were closed without merging. docs/user/COMPATIBILITY.md should describe what main does today.
• The branch now conflicts with main (the table gained a row). Please rebase.
• Once the dependencies have landed, re-run the title on current main, update "Tested" with that run, and fix "Depends on" (drop closed PRs or say what replaces them). Until then this can't merge; it will be closed as stale if it stays without activity.

[oneandonlydean]

Closing: the row has to describe what main does, and #2053, #2054 and #454 are still open; the points from 10-10 are unanswered and the branch conflicts. Please reopen with a run on main once they have landed.