It was likely mentioned before my comment here, but I think I just say it regardless. This is a joke, I get it if the very first time you need to activate something, fine. But on my 2nd start of the sim what the h… do you need to activate? What is not active in your cloud or not active on my computer?
Honestly speaking the amount of time I lost waiting for the sim to start during the last two months can be measure in 10s of hours now, please believe me, it is a fact.
Try to use a different DNS server e.g. Cloudflare.
Thank you for the DNS tip, tried Cloudflare, zero impact on the Activating packages phase. I wait for the next official update then.
Just to be sure:
Router set up
DNS 1.1.1.1
2. DNS 1.0.0.1
together with
DNS IPv4 2606:4700:4700::1111
DNS IPv6 2606:4700:4700::1001
It was running since day 2 for me.
Right now: Hanging on 7% since 2 hours (and a couple of tries)
I never get this unless I pull the network cable before starting the app. Without the Network Cable pulled I get, Loading Languages up to around 7%, Then Just Activating Packages up to 25%, then 5/1010 for around 3 minutes, then Loading World Data up to 68% and then I just hang and sim never loads.
If I pull the Network Cable, I get:
VFS Activating Packages up to 25%, then 5/1010 for around 2 minutes, then Loading World Data up to 68% and then it hangs and sim never loads.
Why does pulling the network cable make it do different start-ups? Tried the Sync Time Fix, Deleting Streamed Packages, and nothing, at the moment, I simply have a game that doesn’t work.
Have you tried this?
Every second loading into FS works fine, if the previous loading stuck at ‘loading language’ process was forcefully killed via alt+tab and shutting down FS24 via task manager.**
For me this is definitely 100% reproducable.
I reported time ago to Asobo the excessive amount of time (around 100 sec on my pc) just to mount the world tin file with an overall of over 200 sec just for the mounting phase during startup
To my knowledge (as I prefer to be out of the beta for my health safeness) that issue should have been fixed now