Rolling cache recommendation

Could the devs please confirm if rolling cache is only recommended where internet data limitations exist?

Or are there any potential use cases where performance would be better with it enabled on an NVME / M.2 drive? If so, is a larger cache size recommended?

1 Like

Vote this up folks. We’ve had so many polarizing threads about it being ON/OFF, it’s effectiveness, and what size and location matters. Plain speak answers from the Devs, please!

I’ll chime in too as the rolling cache is also a cause of CTD while on the Mt. Fuji screen. Deleting this file, allows the sim to load.

What error checking is in place to help prevent unwanted CTD?

Answer: All the rolling cache does is put world data into a FIFO cache on disk so that when flying over an area twice, the data isn’t streamed from the internet again. Each http request will first check the presence of the data on disk before reading it from the internet. Data is not changed in any way and is stored on disk in exactly the same format as it is received from the internet. In some situations, the HDD access may be slower than high speed internet access, but for the majority, the cache will reduce and / or prevent terrain streaming lag. In all cases, the rolling cache will reduce the internet data usage and free up bandwidth for other uses when users fly over the same area again. We recommend a rolling cache of at least 8Gb, 32Gb being enough for most use cases. In most cases the sim will stream world data at an average below 10Mbps. The rolling cache does not impact user experience when they fly over new areas however. We have not thoroughly tested the benefits of creating huge caches of hundreds or thousands of gigs but given how the system works, as the cache grows bigger and bigger, it’s benefits should fade out and it will take a lot of time to even fill up the cache.

Timestamp on Youtube: Will link to this one available