Location of the file for me is in default location
C:\User\ your name\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache
Watch the green lines
DirectX 12 has been an option for what seems like a long while now, and yet I’m unaware of any outcry about it breaking add-ons. Is there a good possibility that the developers’ ongoing tweaking of code is bound to break the add-ons when the beta has not?
I haven’t seen any performance issues. Does this happen only on very long flights. Maybe the addons start slowing it down. So why is this happening
It has happened to me on flights around 1.5 hours upwards using a detailed flight plan and atc.
Now I stick to 1 hour’ish flights and touch wood lately don’t yet seem to have performance issues
I’ve done successful 12 hour flights in the 737-700 BBJ with no slowdowns or crashes, but with the FBW A320 I’ve not been able to fly for longer than 2 hours before things start getting bad. I’ve heard others fly the FBW for 3-4 hours with just a little drop in fps, but it’s difficult to say as the end-user.
Even in P3D the PMDG planes have the best performance. I use a I7 7700k and a 1080 TI. Everything will is set on ultra and nothing slows down. But I have very few addons so maybe that helps
Yes, but I also think this is a sign that the simulator itself isn’t the issue right now. On the contrary, I’d argue that the sim is probably at its most stable state till date thanks to the hard work of the devs over at Asobo. It does however tell us what we already knew; that add-ons can be, and probably are, the root cause of a lot of the issues people have with the sim slowing down and crashing.
I agree with what you said and I think msfs 2020 is pretty good without the scenery addons, but that is just my opinion.
That said, scenery add-ons really shouldn’t be able to crash the sim, unless there are bugs in the sim related to handling of scenery.
I’ve seen many running the sim in 15FPS. When we run it like that either our gpu or cpu has 100% load and that is not good. Makes the sim unstable and often makes my sim CTD. If CTD try have balance cpu and gpu load and have at least 35fps on ground and then lock it at 30FPS then you know your hardware not have completely 100% load when locked at 30FPS. If your FPS get below the locked 30FPS you know either CPU or GPU has 100% load. Then it’s time to balance it out for a different location or plane or other 3rd party addons.
When talking and comparing performance from one person to the next, you’ve also got to factor in the endless variables…
I mean I could say performance is great for me the majority of times… but that’s because I mostly fly around Australia…
Our urban areas are very small when comparing to Europe / the US…
We literally have the entire planet to fly around, so saying I have a 1080ti and can run ultra no problem is about as usefully as saying I can sprint in 9.90 seconds.
If thats the 100m then amazing, if it’s 50m then you’re ****house 
It very much increases the draw distance above 400. I found a happy medium at 5.00 in urban areas, and 7.00 in rural areas. You can see that buildings appear much sooner in the distance, and take much longer to finally melt. I also tested at higher T-LOD up to 9.00 which crushes my system, but defo works
T LoD=5 and O LoD=10 works for me on my GTX 1660TI.
Graphics are great and flight smooth.
Edit:
Just for info.
I ran the O LoD up to 900 and it did not seem to matter to FS2020.
But, I did notice that a couple of times when I forgot to make UserCfg.opt as “Read Only”, FS2020 set it back to 10.
So, I now assume that 10 is the max for O LoD.
I ran T LoD up to 9 but my GTX 1660 TI will slow to a FPS of 3.
The GTX 1660 TI flies fine at T LoD =5.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
