Is there a lighter way of loading a custom asset? We are using the bevy_pathmesh and had a very bad time getting asset loading to work.
We thought we could do everything in a startup system. Looking at the example from that crate, he used a startup system to load the asset with asset_server.load() and then had a second system running, checking if it was loaded and then did the spawning logic.
This approach of having a custom system checking each cycle if the asset is loaded, even after it has been loaded, seems weird to me. Now, looking at the official bevy examples (https://github.com/bevyengine/bevy/blob/latest/examples/asset/custom_asset.rs), I can see this seems to be the default / recommended way.
Is there no other option of awaiting asset loading within a startup system?