August 24, 20205 yr 17 hours ago, dobee51 said: The worst part of the rolling cache is you can't recover that disk space. MSFS 2020 won't let you reduce the size. I wanted to reduce my rolling cache from 250 down to 50, and it told me I didn't have enough space left on the drive. You can easily recover the disk space. MSFS won't let you reduce it, but you can increase it or remove it.
August 24, 20205 yr 6 hours ago, RaptyrOne said: I agree. Firstly, caching scenery to your disc, whether rolling or manual, will require hard disc activity. That implies CPU cycles. That implies additional strain and maybe that explains why switching this off is improving performance for some. Beyond that is the issue of writing to your SSD. Rolling cache is continuously writing to your SSD as you fly. I have always been led to believe that SSD’s lifespan is determined by write cycles. I have both disabled. Fortunately I have a relatively decent internet connection though. I had a 50gb rolling cache and I removed it because while in the sim there was never any activity on the cache drive. Also no difference in performance.
August 24, 20205 yr 1 hour ago, desbean said: I had a 50gb rolling cache and I removed it because while in the sim there was never any activity on the cache drive. Also no difference in performance. I heard rumours the cache doesn't work properly at the moment. Don't know how true it is but I noticed the same lack of activity on the cache drive. Hopefully an update (either of the program or of the documentation about it) will clear things up. Edited August 24, 20205 yr by iwebber Clarity
August 25, 20205 yr I removed it, it removed stutters and gave me shorter loading times. R5 3600 - GTX 1070OC - 32GB 3200 - NVME - 3440x1440 160Hz - VR(Quest 2) GarbagePoster™
August 25, 20205 yr Anyone got those long and complete freezes (like 10 seconds or more) in MSFS? I often got it a few minutes into the flight and then all were good and going on. I set cache to 200GB. Wonder it has sth to do with MSFS downloading and filling the cache in the early phase of the flight. 9950X3D / 64GB / RTX5090 / Pimax Crystal Light / Win11
August 25, 20205 yr 7 minutes ago, FlyIce said: Anyone got those long and complete freezes (like 10 seconds or more) in MSFS? I often got it a few minutes into the flight and then all were good and going on. I set cache to 200GB. Wonder it has sth to do with MSFS downloading and filling the cache in the early phase of the flight. I'm almost sure this is do to do weather loading and not anything as far as the cache/texture loading. ASUS ROG STRIX Z390-E GAMING / i9-9900k @ 4.7 all cores w/ NOCTUA NH-D15S / 2080ti / 32GB G.Skill 3200 RIPJAWS / 1TB Evo SSD / 500GB Evo SSD / 2x 3TB HDD / CORSAIR CRYSTAL 570X / IPSG 850W 80+ PLATINUM / Dual 4k Monitors
August 25, 20205 yr Noticed no difference (reduced performance if anything) with 50GB cache SAR Pilot. Flight Sim'ing since the beginning.
August 25, 20205 yr 2 hours ago, FlyIce said: Anyone got those long and complete freezes (like 10 seconds or more) in MSFS? I often got it a few minutes into the flight and then all were good and going on. I set cache to 200GB. Wonder it has sth to do with MSFS downloading and filling the cache in the early phase of the flight. What is your Terrain and Object Level of Detail sliders set to? These settings are the "distance" away from your plane that the sim begins to load higher level of detail terrain, textures and objects. further away from the plane, the more has to be loaded. The numerical value has not units. but lets say it's in KM.for illustration sake. At a setting of 10, draw a circle around your plane 10 KM away from the plane. The edge of the circle represents where the sim is transitioning from low resolution mesh, textures and objects to high. The amount of work the CPU has to do will be dependent on object density, terrain complexity and texture resolution. Suffice it to say, in very dense urban areas, even areas close to the plane, that can be quite a bit of work. Now expand that to the max of 200 and draw a circle 200 KM out from your plane and see how much more scenery areas alone the sim has to render. Now most of our GPU's have no issues with the rendering part, but it's the CPU that creates the model to render, and you can understand how that can be affected. I can put my CPU from 60% utilization to 100% utilization simply from changing the sliders from 10 to 50. LOD sliders, altitude and speed are all going to play into this. If I'm in dense urban areas, I tend to leave my terrain LOD's unchanged and reign in my object LOD. It causes more object pop in closer to the plane, but limits the pausing. If I'm bush flying, then I have to find a happy medium. Mountain Ranges are going to really ping the terrain LOD, but forests will ping the object LOD so I usually have to reign them both in. If I'm cruising at 31000ft, I don't want to see texture tearing and I'm usually so high, that there are not a lot of objects to render, so I can afford to adjust those sliders to max. I have several settings in my head I swap in and out of depending on what I'm flying, where I'm flying, how fast and high I'm flying.
August 28, 20205 yr Unfortunately, I set FS to work creating a 500 GB rolling cache on an external HDD and THEN decided to look up if there is a recommended size. Realizing that it would take hours and probably isn't worth it for me, I killed the FS process and deleted the incomplete .CCC file (which was up to about 36 gigs after about 20 minutes in my case). But now when I try to start FlightSim it hangs up creating that rolling cache file again. I know that's what is happening because I checked task manager and the folder I had set for the rolling cache and it was busy writing away and creating that file that I had just deleted. So now I'm stuck, because I still don't want to wait hours for FS to start. Does anybody know of a config file, utility program, or some other way I can edit this setting down to something reasonable or turn it off? Thanks in advance. Nevermind. I killed the original restart attempt and on the second time it corrected to 8 GB and the in-game setting reflects that. It's still in the correct directory I set up for it. It's also possible that I was just impatient on my first restart attempt -_-' Edited August 28, 20205 yr by Noew
Archived
This topic is now archived and is closed to further replies.