Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Game: Dead Or Alive 5; executable: game.exe, launched by game.bat.
Discord thread: 1565071668009762856 (https://discord.com/channels/1378308569287622737/1565071668009762856).
Evidence: Mali-G76 System driver with wrapper-gamenative. Report 1565071668009762856 uses DXVK 2.4.1 and Proton 11 ARM64EC/FEX: debug_log.txt L963 reports vkGetDeviceBufferMemoryRequirements Exception 0xc0000005 in Unix call, then L966 exit 3. Report 1565081766346231858 uses DXVK 2.6.1-gplasync and Proton 9 x86_64/Box64: L1543-L1548 reports c0000005, assertion for the same call, then exit 3. Latest direct-EXE report exits before the DXVK banner, so it is not a reproduction of this Vulkan failure. The later memfd_create app teardown failure is separate and is not addressed here.
The three maintenance4 memory-query handlers currently choose native forwarding solely from a non-null dispatch pointer. Android loader trampolines can be non-null without underlying ICD support. Clear those three native pointers when the original base feature snapshot lacks maintenance4, selecting the existing buffer/image create-query-destroy fallbacks and existing sparse fallback. Do not change native-capable devices, shader lowering, game files, Wine, or emulator.
Validation: git diff --check passed; CI compilation pending. Hardware confirmation is still needed. Expected next report: fallback selection log, no vkGetDeviceBufferMemoryRequirements Unix fault, progress beyond device initialization. This is a targeted compatibility fix, not proof that every game startup issue is resolved.