Skip to content

wrapper: correlate startup commands and native fence results for Content Warning - #50

Open
butilly wants to merge 2 commits into
wrapper-25from
fix/content-warning-wrapper-diagnostic-2
Open

butilly wants to merge 2 commits into
wrapper-25from
fix/content-warning-wrapper-diagnostic-2

Conversation

@butilly

@butilly butilly commented Oct 30, 2026

Copy link
Copy Markdown
Collaborator

Game: Content Warning; executable: Content Warning.exe; thread: 1565788402815733800. Follow-up to diagnostic d80181e on Mali-G57, native Vulkan 1.1.191. Latest report: 304 seconds, 4.1 FPS, second VkDevice QueueSubmit seq=1 returns success with two command buffers, first timeline wait returns VK_ERROR_DEVICE_LOST; native fault reporting unavailable. BCn self-tests pass. No identified faulty operation justifies a functional workaround yet. Diagnostic 2 adds bounded first-eight native fence wait and timeline counter results plus first-128 startup command names correlated to submitted native command buffers and fence handles. Existing info/error/bcn and Wine Vulkan logging lack these results; full api_dump depends on an external layer and is unbounded. Preserve command arguments, queue order, return values and timeouts; no additional Vulkan calls. Preserve Proton 9 ARM64EC and DXVK-Sarek. Next report must verify GN-WRAPPER-LOSS-v2 and compare fence completion versus timeline errors on the same device; this is the second and final diagnostics-only build for this thread.

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