Open dndn1011 opened 7 months ago
What's most likely happening is that its trying to stop threads from spinning that never started. When the scheduler moves it has to terminate any spinning threads because std::thread objects cannot be moved from what I recall, which creates a whole hassle of issues.
I'll look into it later today.
Note: for support questions, please use the #engine-user-help channel in our Discord or create a discussion. This repository's issues are reserved for feature requests and bug reports.
Describe the issue: If you create a NovelRT::Ecs::SystemScheduler as a variable which is then later initialised, this generates no compile error or warnings, but the engine will fail due to conflicts caused by thread shutdown in the move function.
I suspect it should not be shutting down the threads when the SystemScheduler is moved.
Please provide the steps to reproduce if possible:
|| V
NovelRT::Ecs::SystemScheduler scheduler; scheduler = Configurator() ...