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: Dying Light (DyingLightGame.exe). Thread: 1558400197086937158.
Latest Legacy LSFG report on Adreno 840 / Proton 9 arm64ec remains at median 0 FPS and asserts in the Wine vkCreateSwapchainKHR host call. Logcat reaches Adopted-device caps immediately before the assertion, without a completed swapchain context. Shader-worker saturation is transient and ends around 13 seconds, so it is not the persistent failure.
The adopted framegen path allocates Core::CommandBuffer below the loader through Volk but omits the loader-data callback already used by Mini::CommandBuffer. Route the private Volk device resolver through a loader-aware allocation adapter, initialize each dispatchable command buffer, and release all allocated buffers if setup fails. Other calls stay on the next-layer device resolver. Add three startup-only fallback-image markers to identify progress through the exact initialization region.
This is a candidate fix, not a confirmed device result. No present-mode, image-count, shader or game-file changes; the Native app backend is unchanged. Verify the new build stamp, fallback descriptor ready, completed LSFG context and rendering with Legacy x2; compare against median 0 FPS and absence of those markers. If the assertion remains, the last marker narrows the next investigation.