Closed janhohenheim closed 1 month ago
@kaosat-dev I have not tested the latest release yet, but from your release notes on Discord, I believe this issue can be closed :)
Edit: closing it myself. I've still not tested your fix, but I'll just reopen if this happens again.
I get this fairly often on Wasm and rarely on native:
My solution for now is to manually preload all materials, levels and blueprints to be safe.
Due to this mainly happening on Wasm, where scheduling is single threaded, and only happening sometimes, I am pretty certain this is due to a scheduling ambiguity.