-
-
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
Simplest possible Bevy app causing console to be full of errors. #13428
Comments
These are graphic driver problems. Have you updated your graphics driver recently? |
Yes after running Bevy app and seeing all those errors I updated all my drivers. |
Also when trying to launch an app in fullscreen mode with this code:
The app crashes and here is console output:
|
Can you test the examples upstream for |
Any specific examples ? |
|
hello_triangle console output:
Running window example from winit doesn't produce any errors |
Okay, looks like a wgpu bug then :) Can you please open an issue there and link this one? |
gfx-rs/wgpu#4247 Actually pretty easy fixable, it's because when initializing wgpu, it registers and VEH and it keeps the DX12 instance open, even though its not used. Theoretically, either removing the dx12 feature, or setting WGPU_BACKEND=vulkan gets rid of this error |
Well setting backend to vulkan does remove the erros from the console but it seems this bug goes deeper because as I said fullscreen mode doesn't work and crashes the app. Also not sure if it's related to that bug but performance is terrible. For example, I've tested really simple tilemap using 2 textures. I've created procedurally map that's 128x128 which is around 16000 sprites and bevy choked. Fps dropped to like 35. Meanwhile libgdx which is java framework rendered map of size 256x256 which is 65000+ sprites and maintained stable 144 fps and that's only because that's my monitor refresh rate. | EDIT: Performance issue solved, it was becaause of that crate called world inspector egui. It was massively slowing down entire app for some reason. |
Were you using a release build (e.g. |
I've checked both debug and release, I've went through all bevy docs including the link you provided. After removing that crate bevy handles maps 1000x1000 tiles with 100fps even in debug mode. Also I've noticed Bevy is using some kind of 2d "culling" by default. The only error remaining is fullscreen mode crashing the app |
Can you open up a new issue for this with details on the OS and hardware used? This is a nice clear problem that would be good to track :) The rest of this is largely resolved: I'm going to close this out now. |
Bevy version
Bevy 0.13.2, 0.13.1, 0.13.0 - tested on those versions.
Relevant system information
Cargo version: 1.76.0
AMD 5 3600
Radeon RX6800
Windows 11 Home
What you did
I just built Bevy and wanted to test if it works so I've added code for the simplest possible app:
use bevy::prelude::*;
What went wrong
The console is full of errors from the start:
Additional information
Not sure what to even include here since I didn't even write any code.
The text was updated successfully, but these errors were encountered: