Skip to content

wrapper: trace Dishonored startup across native Vulkan boundaries - #53

Open
butilly wants to merge 1 commit into
wrapper-25from
fix/dishonored-wrapper-startup-diagnostic
Open

butilly wants to merge 1 commit into
wrapper-25from
fix/dishonored-wrapper-startup-diagnostic

Conversation

@butilly

@butilly butilly commented Oct 31, 2026

Copy link
Copy Markdown
Collaborator

Game: Dishonored - Definitive Edition; executable: Dishonored.exe; thread: 1565803505246150776. Mali-G925, Proton 11 x86_64 and DXVK 2.7.1. Previous run faults with 0xc0000005 in vkCreateGraphicsPipelines; latest run ends after NULL pNext device fallback and canonical nullDescriptor resources without a Wine exception. Existing info logging only reports graphics creation after return, and requested validation/API-dump layers produced no calls. Add per-application, flushed stderr breadcrumbs capped at 256 lines around base device creation, null resource operations, pipeline entry/lowering and driver dispatch, including VkResult. No rendering policy changes in this diff. First diagnostic build; keep Proton major, architecture and DXVK unchanged. The next report must identify the last entered operation without its matching return; timing alone does not establish nullDescriptor as the cause. Base is wrapper-25 6bcfbaa, which differs from the unversioned shipped package and already gates feature-chain fallback, so improved startup alone cannot establish a specific fix.

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