# v0.71 current-build audit Audit date: 2026-09-01 This checklist compares the current runner, prepared data and language packages with the promises published in the v0.71 pre-release. It distinguishes code presence from validation on PlayStation Vita hardware. ## Present in the current runner - Native/Balanced/Performance resolution profiles. - Optimized/None/Aggressive texture profiles. - 30/40/60/Unlocked frame-rate choices and live filter/FPS changes. - Legacy GL default and experimental Modern GL selection. - None, Scanlines, Sharp Bilinear, Dithering and VHS filters. The removed CRT Curvature and Depth of Field experiments intentionally remain disabled. - Chapter-local BC3/RGBA4444 discovery, room-aware eviction, semantic UI/font pinning, progressive 3/15/60/180-frame retry backoff and battle preload. - Localized Loading/Generating overlays and Toby loading animations. - Dynamic, simple (`border_line_simple`) and disabled console borders. - Language UI files/icons, English/Nihongo base mode and translated packages. - Audio transition hold, OGG seek support, stale-buffer recovery and SFX path resolution. - SceAvPlayer video path and shader bootstrap. Hardware playback remains an open validation item, exactly as stated under Known issues. - Trophy list, notifications, persistence, NoTrpDrm bridge, queue polling, stable equipment fallback and automatic local platinum completion. - Probe logging guarded by `devmode=1` and sequential manual rotation. - Shared Chapter 0 build-version marker. ## Prepared texture contract The current contract is: ```text matching data.win + matching BC3 + matching RGBA4444 ``` Direct lossless RGBA8888 upload from `data.win` is not the normal Legacy GL fallback. Missing prepared pages enter the explicit generation path instead. This supersedes the older release-note wording that described an embedded texture fallback. The physical audit reopens every R444 and BC3 file, validates its dimensions, offsets, source size and PVR v3 fields, then checks `complete.vtc`. The audit is implemented by `scripts/audit-v071-cache-contract.py`; targeted R444 repair is implemented by `scripts/repair-v071-r444-contract.py`. Final result: **39 chapter/variant sets checked, 39 passed, 0 failed**. Original Chapters 0, 1, 3 and 4 had missing R444 pages restored; Original/PT-BR Chapter 2 had stale R444 offsets refreshed; PT-BR Chapter 0 had one obsolete extra page removed. Existing BC3 payloads passed validation and were not re-encoded. ## `data.win` caveat Original and most translated Chapters 1–4 contain the mod's 29 gameplay trophy trigger IDs. PT-BR Chapter 1 and Chapter 2 currently do not contain `obj_event_manager` or the original GML trigger calls. Copying whole GML events from another language would overwrite translated game logic, so the audit does not perform that unsafe replacement. This remains a separate builder task. No `data.win` was regenerated by this release audit. Therefore texture-page indices did not change and no BC3 rebuild was required by the runner/trophy changes through VPK v0.71-86. The cache repair only restores R444 files and headers against their existing matching `data.win` files. VPK v0.71-89 adds an independent runtime BC3 fallback for Aggressive mode. It does not modify `data.win`: missing or stale BC3 pages are derived from the active file on the Vita, written atomically and tied to the current TXTR layout through `complete.bc3.vtc`. Critical font/UI pages remain R444. VPK v0.71-90 adds the localized `UPDATING / game files` loading state and its safe migration contract. The state remains dormant until a compatible, versioned migration exists; it must not imply that the Vita can perform a full UndertaleModTool/DeltaBuilder rebuild. ## Still experimental or pending hardware proof - Modern GL rendering and Chapter 5 city shadows. - Chapter 3 VHS audio/video presentation on Vita. - Chapter 3 first-use battle stalls. - Chapter 5 final-battle memory and frame-time pressure. - Full gameplay-trigger trophy coverage in PT-BR Chapters 1 and 2.