I heard having the rolling cache enabled is the cause of stutters which some users are experiencing.

9 minutes ago, Peter Webber said:

I heard having the rolling cache enabled is the cause of stutters which some users are experiencing.

I have wondered if size has something to do with it. I resized to 50 GB, but I'm thinking that "searching" this 50 GB might introduce a performance penalty. It takes so long to just resize a cache that it makes me question how optimized the cache database is. On the other hand, my Internet is not the fastest, so if working properly the cache should greatly improve performance over areas I've previously flown over.

My current thinking is to reduce the rolling cache size and rely on the manual cache for photogrammetry, but I'm reading elsewhere that we cannot shrink the caches once they've been made bigger. Oi!

On 8/20/2020 at 4:10 AM, RaptyrOne said:

"... It would have been nice if a basic manual had been published to explain these intricacies - how these caches work, how best to set them up to take max advantage of them, what happens if a 3rd party add on is installed to a pre-cached area, or if Asobo themselves update scenery files that affect a pre-cached area? Does the Sim recognise the new data and auto-delete the "outdated" cache data?"

Well said, I could not agree with you more. That MS/A did not include a .pdf version of a manual for software of this magnitude is inexcusable, and I would say disgraceful. Help menus, YouTube videos made by enthusiasts, and tutorials spread around the internet are fine and dandy; but producing a complex product such as this piece of software without a manual or without comprehensive documentation is akin to Garmin not offering manuals for their products (Garmin has a robust support section wherein product manuals may be downloaded in .pdf format), or Nikon not having a manual available for its D6 camera (320 pg. pdf manual available here-  http://download.nikonimglib.com/archive4/0jPaM00RmG8X04OHmHu51zF0mV11/D6UM_EU(En)01.pdf).

Hey, before we hop in our airplane with the newly installed Garmin unit, and before we take photos of our destination when we arrive there, let's simply watch a YouTube video or two, let's just ask friends & contemporaries (not experts) lots of questions, and then, hey, le't just start pressing a bunch of buttons! Yaayyy!!!

(ps: been flight-simming since the big-bang)

Edited September 5, 20205 yr by RustyFlyer

On 8/25/2020 at 1:19 PM, Will Fly For Cheese said:

I set Rolling Cache to 100 Gig and Manual Cache to 100 Gig and still today I flew an area I've flown around at least 6 times in the last few days and I used over a gig of downloaded data.

I think they're a bit broken at present and not working as designed.

 

This might explain the CTD issue when flying long distances over land (especially in the Longitude).  

Hello!

There is a way to change the size of the manual cache, imho:

I have set my first manual cache to 300GB and then decided that I wanted it smaller. For this 1st attempt I created a folder on my SSD where MS FS stores the cache. I didn't want to just delete this file because I feared that MS FS would crash.

So, I made a new folder (old: \MS FS 2020 manual cache, new: \MS FS 202 manual cache 01), started the sim and pointed the sim to the new folder, setting the size to 3GB (if you change the path, MS FS lets you set a new size!).

After MS FS created the new 3GB cache file, I simply deleted the "old" one.

1 hour ago, Seabhag66 said:

Hello!

There is a way to change the size of the manual cache, imho:

I have set my first manual cache to 300GB and then decided that I wanted it smaller. For this 1st attempt I created a folder on my SSD where MS FS stores the cache. I didn't want to just delete this file because I feared that MS FS would crash.

So, I made a new folder (old: \MS FS 2020 manual cache, new: \MS FS 202 manual cache 01), started the sim and pointed the sim to the new folder, setting the size to 3GB (if you change the path, MS FS lets you set a new size!).

After MS FS created the new 3GB cache file, I simply deleted the "old" one.

So here is an idea - since adding new regions to an existing cache slows it down considerably, could one not have a collection of sub-directories, each with its own manual cache? For example - C:\Cache\Boston and C:\Cache\New York. If I know I'm flying to one of these cities, I just change the path to point to the desired cache. This would allow me to cache a dozen different cities without the dreaded unresponsiveness that occurs when using one single huge cache.

19 minutes ago, Keto Ketchup said:

So here is an idea - since adding new regions to an existing cache slows it down considerably, could one not have a collection of sub-directories, each with its own manual cache?

Do we know this?? How??

4 minutes ago, Bert Pieke said:

Do we know this?? How??

It's just a hypothesis at the moment. I'm setting up some directories now so I can try it later on.

So I've created two manual cache's - New York 13.47GB and Seattle 20.44GB - the manual cache interface is now totally unresponsive - EDIT very very slow to navigate. 

Someone touched upon this earlier if I remember.

I created a three layered LOD 'big" manual cache for the Vancouver city area and it says its 4 MB "big" after 5 minutes of work, yet a similar area for Seatltle came in over 6G

????

And yeah, after using the manual cache a few times, even the buttons become unresponsive or take a couple minutes to just clear the naming box using the backspace key. and me with 16 threads CPU

HAHAHA

Edited September 5, 20205 yr by peppy197

The good news - I tested out Seattle, absolutely fantastic with photogrammetry rendered perfectly.

The bad news - I can no longer create anymore cache areas as the SIM becomes completely unresponsive - I have fraps running - my FPS drops to 2 within that screen - bug for sure 👍

Edited September 5, 20205 yr by hanhamreds

5 hours ago, Keto Ketchup said:

So here is an idea - since adding new regions to an existing cache slows it down considerably, could one not have a collection of sub-directories, each with its own manual cache? For example - C:\Cache\Boston and C:\Cache\New York. If I know I'm flying to one of these cities, I just change the path to point to the desired cache. This would allow me to cache a dozen different cities without the dreaded unresponsiveness that occurs when using one single huge cache.

My initial tests appear to be working! I'm creating multiple cache files, each dedicated to a single city and surrounding area (unless there happens to be multiple cities in close proximity). The biggest negative with this is that I have to manually select the cache for the area I'm going to explore, but it beats the alternative of having to delete regions to make the manual cache paint tool responsive.

Hopefully this is just a short term bandaid until the manual cache "painter" tool is fixed.

Have tried both and noticed nothing positive. Tried Ultra for city and medium for larger urban area(s). Will likely delete them all.

2 hours ago, peppy197 said:

I created a three layered LOD 'big" manual cache for the Vancouver city area and it says its 4 MB "big" after 5 minutes of work, yet a similar area for Seatltle came in over 6G

????

And yeah, after using the manual cache a few times, even the buttons become unresponsive or take a couple minutes to just clear the naming box using the backspace key. and me with 16 threads CPU

HAHAHA

Most Canadian cities are missing photogrammetry.  For Vancouver, the only photogrammetry is downtown Vancouver and a little outside of downtown.  Otherwise, for most of metro Vancouver, there isn't any photogrammetry.  One way to check is just go to Bing Maps and you can see which areas of the city have photogrammetry.

So that's why if you try to cache parts of the Vancouver metro area, it's 4 MB.  Conversely, much of metro Seattle is covered by photogrammetry.  So that is why caching metro Seattle may give you 6 GB.

You can just do a visual check.  Fly a slow plane like the Cessna 152 close to the ground.  Metro Seattle looks way, way better than metro Vancouver (only downtown Vancouver looks good because it has photogrammetry).

Creating manual cache just makes the whole thing nearly unresponsive after a while. And I only cached Oslo and surrounding areas at medium, and some downtown areas as High.