I thought it would be interesting to make some comparisons, between spawn times for streamed content and installed content, since this option is a new feature, introduced in SU3.
I tried this test with different air traffic settings, as that had an effect on my spawn times in the SU2 beta, as noted in this post, but that had seemingly no significant effect, in this SU3 beta.
The tests were conducted such, that I first spawned into the airport (KDFW, part of WU2), in the plane of choice (C172 Basic), so that everything was cached and ready. I then noted the time it took between clicking ”Start flight”, until I saw the ”Ready to fly” button. I’m on a Xbox series S, 32 GB rolling cache, 250 Mbit Internet connection.
SU3 Beta, v. 1.5.1.0
Streaming
KDFW, Dallas, Cessna 172 Basic, Gate C2
Live Traffic | AI Traffic | Traffic Off |
---|---|---|
32 sec | 30 sec | 29 sec |
28 sec | 31 sec | 29 sec |
31 sec | 29 sec | 28 sec |
Installed
KDFW, Dallas, Cessna 172 Basic, Gate C2
Live Traffic | AI Traffic | Traffic Off |
---|---|---|
28 sec | 28 sec | 28 sec |
28 sec | 28 sec | 28 sec |
28 sec | 28 sec | 28 sec |
Before I started timing the installed spawns, I again spawned in once first, as I noticed that the airport was not immediately rendered while in the menu. Presumably it has to re-render from the installed files, rather than the cache, on first spawn.
Conclusion? It was at least very consistent spawn times with the files installed, but the benefit is either marginal or inconclusive. Small sample size, and all that. It certainly didn’t hurt the spawn times, at least.
As a bonus test, I timed spawning in a plane on an airport where both definitely weren’t in the cache prior to test. First v second spawn, both streamed and installed.
Airbus A330, KATL (WU2)
1st | 2nd | |
---|---|---|
Streamed | 1:37 min | 0:54 min |
Installed | 1:29 min | 0:55 min |