Skip to content

wrapper: trace BioShock device startup boundaries - #44

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

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

Conversation

@butilly

@butilly butilly commented Oct 29, 2026

Copy link
Copy Markdown
Collaborator

BioShock Remastered (BioshockHD.exe), Discord thread 1565409539027632220. Mali-G925, Proton 11 arm64ec with 32-bit guest, Wrapper-gamenative/System. Latest report ends at Emulating nullDescriptor with canonical zero resources; median 0 FPS, Main Game Thread 18%, manual quick-menu exit. This message follows successful base-driver device creation, so it does not establish a native vkCreateDevice hang. Existing info/error logging does not bracket null-resource calls or subsequent queue setup; capability diagnostics occur only at the end. Diagnostic 1: log entry, completion and VkResult for null-resource driver calls, plus native device creation, dispatch loading, query-reset initialization, queue creation and BCn initialization/prebuild boundaries. Output is unconditional stderr with process ID so a card run needs no additional environment settings. No feature, queue, fallback or rendering behavior changed relative to base 6bcfbaa. Proton major and architecture unchanged. Validate compilation in CI; next device report should identify the last unmatched begin marker or show successful return. This is not a confirmed hang 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