Rolling Cache is referred to in terms of Gigabytes of disk storage.
Mine is set to 16 GB. (8 bits = 1 Byte) On my C: (boot) drive.
Some of you are talking about Mbps (Megabits per second).
This is the speed of your internet from your ISP (Internet Service Provider).
Mine is 200 Mbps from Spectrum via cable to house.
I’m connecting to the FS2020 MS Cloud via my 5G Wireless Router.
Just checked it using speedtest.net. 240.90 Mbps.
Yes, set size to its default, 8 GB.
But, I move Rolling Cache file location to other SSD drive (not in default location C:\Users…), plus I add its location to Exclusion list of Windows Security (Defender).
I delete and create again every time after update.
For my case, whether it is turned on or not, does not have much effect on the FPS (performance).
Not “Everyone” is, most if they use it have given a GB value.
your assertion that there is no relationship between why someone would use it or not and their internet download speed potential is a bit wide of the mark, as they do have some relevance to one another, especially if their internet speed is at the lower end of the scale and they wish to avoid repeatedly downloading the SAME data for an often travelled area.
Forgive me if this is a dumb question, but how do I set mine to 32g? Is it just in the DATA settings. Mine says unlimited right now but if turning rolling cache on and setting limit to 32 is a good spot I would love to try it.
If you could explain how I do this I would much appreciate it.
I have been using the same setting (64GB) for quite some time with no issues.
When we had the problem with stutters and FPS drop, I tried reducing, disabling,… to no avail of course so reverted back to the same.
I don’t see the point of Rolling Cache
If you have fast internet, it’s not really needed since you can probably stream it faster than off an SSD
If you have slow internet, it would take tens of hours flying slowly over the same location to fully download a small area (Isn’t NY City like 40gb of data itself?)
There is no good reasons to place rolling cache on SSD. As any other constantly rewriting things it brings early death to costly hardware and give no benefits in performance because demands of cache reading are compete with mediocre internet connection which times slower than average hard drive.
@ [SalvoVulpine] you are able to preload sceneries without flying. Slow/fast connections are not binary options switching instant to hours of waiting. In most cases you are just able to lower unnecessary traffic by reusing data.
Not entirely true, and pretty much a moot point by today’s standards. SSD’s, such as my Samsung 860, have a TBW endurance of around 1200TB. That is, it will take 1200TB’s of data being written before it’s “life” could be potentially shortened, and in real life tests they even exceeded 2000TB’s before sectors/blocks had to be reallocated. The concerns of SSD wear are a thing of the past, (with the correct type of drive of course).
No, it runs worse for me with rolling cache. The process that updates the rolling cache takes extra CPU time, memory and disk I/O. My internet doesn’t compete with disk access and freeing up the data instantly instead of queuing it up to be stored on disk saves memory.
It does run slightly better when flying the same part over and over since London can demand over 100 mbps to keep up (and even though your internet might easily handle that, I’ve seen the game throttled to 40 mbps at times, other times it will go fully over 100mbps in London). London is also over 40GB of data so better have a big enough cache to match.
However since I always fly somewhere new, there is no point in using the rolling cache.