Significantly longer load times after 1.34.10, often followed by CTD

[JetNoise9515]

But fo ALL of us, the simple trick is:
Stay away from Betas …
or accept the pain

[Wined2310]

Not participating in a BETA is only delaying the issue for all of us, not solving it

[RXN6085]

I can confirm it’s much better in 1.34.14 than in 1.34.10.
I again compared my load times and found the load time increase from my 3 problematic packages has dropped from several minutes to ~35 seconds. I think that’s still too much tbh though, as these packages aren’t big at all in terms of GB, and should, from comparisons to similarly sized unproblematic packages, not make any noticeable impact in loading times at all. However that is still the case with 35s increase.

[NixonRedgrave]

@NixonRedgrave

Load time with the 3 airports installed: 5:00

I finally updated this PC that I’d been doing the vast amount of my beta testing on.

With 1.34.15.0, I seem to have lost some load time. I’m now up to 06:18. That’s a pretty big loss from 05:00 in the previous version.

[RagingWombat839]

I just retimed .15 with my full cold start at 7:20 where with .14 I was seeing 7:08-7:10. That difference is small enough it could be be noise.

[Jingle1966]

Samsung 970 EVO 4Tb

Not necessarily longer loading times, but a few crashes (just silently closing the startup window) which I never had before.
Also once while zooming in on the world map.
One was even so bad, that I had a complete screen freeze for more than a minute (did a hard reboot to get out)
Overall, poor performance (in VR).

openXRtoolkit shows GPU has lots of room (turned down some textures) but CPU constantly in overload.
(Using exact same settings as with official SU12 release)

Also tried DX12, which seems to use less VRAM than before, but eventually still passing max VRAM, and grinding.

3080TI / i9-1100K

[TFEV1909]

Just to confirm seeing normal load times in .16.

[BlackSanta512]

Same here.

[RagingWombat839]

So it’s great that this problem is resolved but it’s also kind of worrying that Asobo admitted in today’s dev livestream that they didn’t ever repoduce or fix this problem and that it just went away by itself. That doesn’t inspire me with confidence that it won’t come back and bite us again.