Skip to content

wrapper: inspect Dishonored pipeline inputs at the native dispatch boundary - #54

Open
butilly wants to merge 2 commits into
wrapper-25from
fix/dishonored-wrapper-pipeline-diagnostic
Open

butilly wants to merge 2 commits into
wrapper-25from
fix/dishonored-wrapper-pipeline-diagnostic

Conversation

@butilly

@butilly butilly commented Oct 31, 2026

Copy link
Copy Markdown
Collaborator

Dishonored - Definitive Edition, Dishonored.exe, app thread 1565803505246150776. The first diagnostic reaches the swapchain and logs graphics count=1, stages=2, pNext present, renderPass null; inline=1 fold=0 legacy=0 divisor=1 stride=0. The base graphics call never returns, followed by c0000005 and winevulkan vkCreateGraphicsPipelines assertion, exit 3 after 16 seconds. Those allocation-path flags do not identify actual inline modules or vertex divisors. Existing wrapper logging only reports pipeline results; external validation and API-dump layers were unavailable. Second and final diagnostic: log bounded input/output pNext types, rendering formats, module handles and tracked SPIR-V hashes, actual materialized module count, divisors, dynamic states and base/requested capabilities. Application scoped, first two calls only, existing 256-line flushed cap; no graphics behavior changes. Preserve Proton 11 x86_64 and DXVK 2.7.1. Next report must identify the concrete structures reaching the base driver before selecting any workaround. Reviewed diff; diff --check passes; CI builds the package.

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