I'm trying to run 'bevy/examples/2d/move_sprite.rs'. The result ist an empty window. The sprite asset is loaded.
- Bevy-0.10
- Windows 11
- x86-64
- Vulcan driver
Ist it a bevy bug, or my stupidity?
#2D Sprite Not renderd
fierce mango
versed fog
Did you copy the example or are you running it from the repo?
If you're not in the repo it's not going to find the image its trying to show
fierce mango
I'm running a copy, and made a asset folder with the PNG at The right location. There ist no error or warning in the console diagnostic output.
fierce mango
Now I cloned bevy-latest and ran '--example move_sprite'. The result is the same. No sprite shows up in the window.
clever tiger
Same issue here - the sprite example compiles on both bevy 0.9.1 and 0.10.0, but sprites do not get rendered on 0.10.0.
clever tiger
Tried with and without dynamic linking, at different opt levels, after cargo clean... no difference.
Attached is a minimal example.
My config is as follows :
2023-03-08T22:13:33.529141Z INFO bevy_render::renderer: AdapterInfo { name: "Intel(R) UHD Graphics 620", vendor: 32902, device: 22807, device_type: IntegratedGpu, driver: "Intel Corporation", driver_info: "Intel driver", backend: Vulkan } 2023-03-08T22:13:34.564716Z INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Windows 10 Enterprise", kernel: "19044", cpu: "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz", core_count: "4", memory: "7.9 GiB" }
I will post an issue on the github tomorrow after trying out a few more things.
fierce mango
Tried it on another PC with windows 10. It is showing the sprite.
clever tiger
Weird. What are your GPUs on both machines? Integrated or dedicated?
fierce mango
In the bad case it is an integrated Intel GPU, the good case is a dedicated nvidia Geforce GTX 1050
clever tiger
alright
Since I also have trouble with an intel iGPU I do think we're having the same issue
and I didn't see anything that could invalidate my example code in the changelog
oh well, no depth prepass for me until this gets fixed I guess :/
clever tiger
@fierce mango As a workaround, you can try setting the backend to DX12 for now - it worked in my case. set WGPU_BACKEND=dx12 before cargo run.