Skip to content

Wheel World: auto-start bounded PowerVR wrapper diagnostics - #42

Open
butilly wants to merge 1 commit into
wrapper-25from
fix/wheel-world-wrapper-diagnostic
Open

butilly wants to merge 1 commit into
wrapper-25from
fix/wheel-world-wrapper-diagnostic

Conversation

@butilly

@butilly butilly commented Oct 28, 2026

Copy link
Copy Markdown
Collaborator

Game: Wheel World; executable: Wheel World.exe; thread: 1565070278357291029. The latest report uses Wrapper-gamenative/System over PowerVR, Proton 10 x86_64, Box64 0.4.2 and DXVK 2.4.1 GPLAsync. Rendering remains garbled on both DXVK 2.4.1 and 2.7.1. The guest environment contains WRAPPER_DIAG=1, but neither a WRAPPER_DIAG block nor a diagnostic attachment was returned. The installed wrapper logs Forcing device creation with a NULL pNext chain. Median fps is 60 without thermal throttling. Existing source already contains capability and BCn diagnostics; the explicit enable test failed, so pin a verifiable diagnostic package. Scope auto-start to the exact executable on the Imagination driver, emit an early marker and primary/retry device results, keep stderr attached to the launcher, mirror capabilities through the existing diagnostic writer, and cap format/copy and CPU texture records. Do not dump raw texture bytes in this capture. No rendering policy change relative to base 6bcfbaa. Preserve the current Proton major/architecture and DXVK. Verification: git diff --check; package CI. Device follow-up must verify wheel-world-wrapper-diag-v1, native versus advertised capabilities, feature-chain result and actual texture storage/upload path. The installed base revision is unknown, so visual improvement alone must not be attributed to instrumentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant