Closed igorlp closed 6 days ago
Also happens on Bevy example found here
How do you see that issue in Wasm? It's supposed to stay black...
Issue does not appear on the WASM example; the make_visible
system runs fine, and all other Update
systems in the example function normally.
Perhaps they were trying to say that it appears if you run the example locally?
Can you try just before and after https://github.com/bevyengine/bevy/pull/14023 please?
Perhaps they were trying to say that it appears if you run the example locally?
Correct!
Can you try just before and after https://github.com/bevyengine/bevy/pull/14023 please?
Works with:
bevy = { version = "=0.14.0-rc.4" }
bevy_winit = { version = "=0.14.0-rc.4" }
Does not work with:
bevy = { version = "0.14.0" }
bevy_winit = { version = "0.14.0" }
(used bevy_winit to trigger other bevy packages to be downgraded to rc4, not sure if issue is related to bevy_winit itself)
Little update: this issue can not be reproduced on the current main
on Intel macOS or Linux (both with or without Wayland).
It really does seem to be Windows-specific.
Bevy version
0.14
Relevant system information
What you did
Set visible: false on WindowPlugin
What went wrong
Systems added to "Update" no longer trigger.
Using:
If visible is set to false by default, we only see
0
in the console, once. If set to true, we see the frame count as expected for every frame.Additional information
Also happens on Bevy example found here