-
-
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
Massive validation errors on Intel graphics, sometimes crashing #6746
Comments
I just started seeing this (?, at least very similar) today. The thing is, I successfully ran my bevy app for a couple of days on this system without any of these validation errors. Under wayland / sway. Intel UHD 770, bevy 0.9.1 So I'm pretty sure it's due to some system changes I made recently, but I have yet to figure out the culprit. my output
|
Turns out I had installed the arch package |
@martinlindhe that may still be an issue, because Vulkan validation layers actually, well, validate the correct usage of Vulkan API, and something is probably set up incorrectly. |
Absolutely so. For me, I think this is error is more relevant for someone programming/debugging a vulkan api user such as bevy, but perhaps not so much for a bevy user who is debugging their game (me). |
Validation errors are supposed to be debug messages. If you don't have the package, the error is still there, just not reported. I am reporting this because it might show underlying bugs of the bevy engine. |
I also get this same error on Intel IGP. I believe once per image load. |
My Anyway, just adding my "can reproduce." |
Bevy version
0.9 stable.
[Optional] Relevant system information
If your bug is rendering-related, copy the adapter info that appears when you run Bevy.
What you did
Try any rendering example, such as
2d_sprites
.What went wrong
Massive amounts of Vulkan validation error. In my developing game, if I spawn too many entities, the renderer actually crashes my entire window system. I have reported validation errors on the same machine before: #5890, but that is a different problem, I think.
The text was updated successfully, but these errors were encountered: