-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Text Glitching [Rendering Issue] #8894
Labels
A-Rendering
Drawing game state to the screen
A-UI
Graphical user interfaces, styles, layouts, and widgets
C-Bug
An unexpected or incorrect behavior
D-Straightforward
Simple bug fixes and API improvements, docs, test and examples
O-Windows
Specific to the Windows desktop operating system
S-Needs-Investigation
This issue requires detective work to figure out what's going wrong
Comments
This looks similar to #7944 |
I agree, I'm running Vulkan. How do I use DX12 to verify that's the cause? |
Do you get the same corruption when you use |
Issue not present with Text2dBundle! Notable overlap between the issue and reproducible test cases: |
github-merge-queue bot
pushed a commit
that referenced
this issue
Jul 19, 2023
# Objective Fixes #8894 Fixes #7944 ## Solution The UI pipeline's `MultisampleState::count` is set to 1 whereas the `MultisampleState::count` for the camera's ViewTarget is taken from the `Msaa` resource, and corruption occurs when these two values are different. This PR solves the problem by setting `MultisampleState::count` for the UI pipeline to the value from the Msaa resource too. I don't know much about Bevy's rendering internals or graphics hardware, so maybe there is a better solution than this. UI MSAA was probably disabled for a good reason (performance?). ## Changelog * Enabled multisampling for the UI pipeline.
I'm seeing the same issues, but with more than just UI. I also see it with sprites. SystemInfo { os: "Windows 11 Home", kernel: "26100", cpu: "AMD Ryzen 7 3700X 8-Core Processor", core_count: "8", memory: "31.9 GiB" }
AdapterInfo { name: "AMD Radeon RX 6700 XT", vendor: 4098, device: 29663, device_type: DiscreteGpu, driver: "AMD proprietary driver", driver_info: "24.12.1 (AMD proprietary shader compiler)", backend: Vulkan } Screen.Recording.2025-01-27.135154.mp4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-Rendering
Drawing game state to the screen
A-UI
Graphical user interfaces, styles, layouts, and widgets
C-Bug
An unexpected or incorrect behavior
D-Straightforward
Simple bug fixes and API improvements, docs, test and examples
O-Windows
Specific to the Windows desktop operating system
S-Needs-Investigation
This issue requires detective work to figure out what's going wrong
Bevy version
Crates:
bevy = "0.10.1"
json = "0.12.4"
regex = "1.8.4"
[Optional] Relevant system information
SystemInfo { os: "Windows 11 Home", kernel: "22621", cpu: "13th Gen Intel(R) Core(TM) i5-13600KF", core_count: "14", memory: "63.9 GiB" }
AdapterInfo { name: "AMD Radeon RX 6700 XT", vendor: 4098, device: 29663, device_type: DiscreteGpu, driver: "AMD proprietary driver", driver_info: "23.5.2 (AMD proprietary shader compiler)", backend: Vulkan }
Windows 11 Home (22H2) [22621.1848]
Up-to-date Windows
Up-to-date AMD drivers
Steps to reproduce
Link to commit with issue
What went wrong
Text is 'glitching' on my Windows machine, as shown in the following screenshot:

This issue is NOT reproducible on my NixOS machine, but is reproducible on both of my Windows 11 machines (possibly of note: both are using AMD cards).
It's not an issue with my text files, I tested some basic ones. The pattern of glitching is the exact same each startup, regardless of window position or size. Changing the position or scale of the text will result in the pattern changing, so I suspect this is a rendering issue.
The text object is generated per The Book's example:
It's brought in via a startup system with the following setup:
And finally, the plugin is dropped into the main app:
The text was updated successfully, but these errors were encountered: