chat: work around Direct3D 11 rendering artifacts on win11 arm #3450
+41
−12
Conversation
This file contains 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
Signed-off-by: Jared Van Bortel <[email protected]>
Signed-off-by: Jared Van Bortel <[email protected]>
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.
The Direct3D 11 scene graph backend shows rendering artifacts on my Windows 11 ARM laptop.
System Model: Dell Latitude 7455
SoC: Snapdragon X Elite X1E-80-100
OS: Windows 11 Pro 24H2 build 26100.2894
GPU: Qualcomm Adreno X1-85
GPU Driver Version: 31.0.80.0 (10/28/2024)
They look like this:
Also, the (hidden) LocalDocs drawer sometimes pops in and out of visibility while the model is generating a response.
None of these issues happen on the Direct3D 12 backend, so let's use that by default on Windows ARM.