Closed InnocentusLime closed 1 year ago
Aren't you forgetting to add the collection to the loading state? Try adding
.add_collection_to_loading_state::<_, Collection>(Loading::Loading)
to your app after you add the loading state.
Aren't you forgetting to add the collection to the loading state? Try adding
.add_collection_to_loading_state::<_, Collection>(Loading::Loading)
to your app after you add the loading state.
Indeed! Sincerest apologies.
I have updated the examples to have the collections actually set to be loaded. Seems the problem needs two asset loads in a row to happen
Thanks a lot! I was able to reproduce and fix your issue :+1:
System configuration
OS: Windows 11 Bevy: 0.10.1 (from crates.io)
rustc --version
:rustc 1.68.2 (9eb3afe9e 2023-03-27)
rustup default
:stable-x86_64-pc-windows-msvc
What versions the problems happens on
This problem happens with
bevy_asset_loader 0.16
and the latest version on the github (when I fetched it the latest commit was 5cd90672eb5b9a8a2127bd225c3f9d3a57c963d4)The issue
I have been trying to implement some multistep loading in my game prototype by having two states -- one that tracks loading and the other tracks the game state.
It seems that
bevy_asset_loader
does something incorrect in such configurations and the assets don't get loaded.Minimal examples
Program 1 (Single probing)
Program 2 (repeated probing)
What you expected to happen
The first program shouldn't crash. The second program should have printed
probe: true
What happened
The first program crashed
The second program not only prints
false
, but also never printstrue