Global Clock initialization order

Michal Páleník 3 years ago updated by Lazlo Bonin (Lead Developer) 3 years ago 2

We recently updated both Unity and Chronos and we came across an error during GlobalClock initialization. There is hierarchy of clocks but children are initialized first and since Timekeeper doesn't know about their parrent at that time, exception is raised. I don't know if you somehow prioritize order in which the clocks are initialized but from a first glance at code it seemed to me that you don't.

Chronos Version:
Unity Version:
Pending Review

Hi Michal,

I see you're using Chronos v.2.2. Fixes to the initialization order were introduced in 2.2.1, 2.4.5 and 2.4.5 (see the changelog). Could you upgrade to the latest version and tell me if the issue persists?