So I just did a quick first test:
- First run
- ensured proper time sync (which is automatic on my system … but it seems like Windows is still a little “lazy” in when it performs the automatic time sync)
- launched FS2024
- finished launch in around 4 minutes
- Second run
- intentionally moved my clock 2 hours into the future
- launched FS2024
- got stuck at “10% Activating packages” … for over 10 minutes
- killed FS2024
- Third run
- manual sync of the clock to proper time again
- launched FS2024
- finished launch in around 4 minutes … again
OK … I think the “evidence” is clear. If your clock is out of sync … you will have (lots?) of problems.
Now I do not want to sound disrespectful, FS2024 is such an amazing piece of software that I joyfully spend lots of my precious short goose life time with it, but if some of the server API actually really was designed with the assumption that every client will have a perfect local clock … then I would count that as a classical beginners mistake. I have see this so often “in the wild” that it is not even funny, and I would not be surprised.
But perhaps Asobo is even the victim in this case, because maybe that is a “feature” of some essential access control API which is provided by the Xbox ecosystem. Time will tell.
I am looking forward to the next dev stream.
UPDATE: Just to give proper credit … it looks like the first to recognize this issue was @BernardBx