Incorrectly specified that system couldn't already exist
Highlight difference to ScriptBehaviourUpdateOrder.AppendWorldToCurrentPlayerLoop
What is the current behaviour?
Unity's existing solution World.GetOrCreateSystemsAndLogException instantiates all system's before calling ComponentSystemBase.OnCreate on each system.
This means that systems calling world.GetOrCreateSystem in their own OnCreate method may get back a system instance that has not yet had OnCreate called.
This is particularly problematic for TaskDriver instances that need system references to be fully initialized to configure jobs against the system's exposed data.
What is the new behaviour?
Executing world.GetOrCreateSystemsSequentiallyAndLogExceptions will create each system in the list sequentially (if required) calling ComponentSystemBase.OnComplete on the system before progressing to the next system.
mbaker3
commented
1 year ago
Create
WorldExtensionand a method to bulk create systems sequentially ensuring each system has completedOnCreatebefore moving to the next system.Tag Alongs
WorldUtil.SetupTopLevelGroupsInCurrentPlayerLoopImprove docsScriptBehaviourUpdateOrder.AppendWorldToCurrentPlayerLoopWhat is the current behaviour?
Unity's existing solution
World.GetOrCreateSystemsAndLogExceptioninstantiates all system's before callingComponentSystemBase.OnCreateon each system.This means that systems calling
world.GetOrCreateSystemin their ownOnCreatemethod may get back a system instance that has not yet hadOnCreatecalled.This is particularly problematic for
TaskDriverinstances that need system references to be fully initialized to configure jobs against the system's exposed data.What is the new behaviour?
Executing
world.GetOrCreateSystemsSequentiallyAndLogExceptionswill create each system in the list sequentially (if required) callingComponentSystemBase.OnCompleteon the system before progressing to the next system.What issues does this resolve?
What PRs does this depend on?
Does this introduce a breaking change?