You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any reason that FrameProviderDispatcher starts on _Ready not _EnterTree?
As it is an autoload it should work fine either way, and using _EnterTree instead means R3 is available on _EnterTree for other singletons and nodes in the scene.
I'm happy to submit a PR if this is ok.
The text was updated successfully, but these errors were encountered:
Thank you.
The optimal placement would be where it's first called from the engine.
It seems EnterTree is called before Ready - I see, EnterTree would be more appropriate!
Is there anything called before this? If not, let's go with EnterTree.
Hey, amazing library!
Is there any reason that FrameProviderDispatcher starts on _Ready not _EnterTree?
As it is an autoload it should work fine either way, and using _EnterTree instead means R3 is available on _EnterTree for other singletons and nodes in the scene.
I'm happy to submit a PR if this is ok.
The text was updated successfully, but these errors were encountered: