Hey @gordongreig I have everything turned off. I don’t play with any traffic besides the vatsim traffic.
I’m going to do some benchmarks here at JFK with the rendering scale. I’ll post screenshots
if the gpu usage is over 80% then it’s acceptable, because the optimisation of this game is broken. I just change the “Terrain level of detail” and “Objects level of detail” in graphic settings from 200 to 100 then this game is limited by GPU : )
I’m currently running the sim right now and I’m getting 20 logical processors. Is that good?
Yes that shows hyperthreading is enabled on your system.
Have you enabled XMP?
Not yet, do I choose either one? I have XMP I and II
Set it to XMP I, and if you get any instability change it to XMP II.
Be sure it matches your ram speed - 3600mhz.
Holy ■■■■ , just tried LA and man was that unplayable! Not even my 2080 super gave me this problem in LA. Maybe I need to turn on the rolling cache for that area
Okay bingo got the speeds to 3600mhz
1 Like
Set render scaling to 200.
It won’t improve your frame rate but will make your GPU work harder and give you slightly sharper images. At this moment, this is probably the best way to make your GPU worth it.
Next patch is said to reduce certain CPU bottleneck so you can have better GPU utilization if not at > 90% already
1 Like
Well gentlemen, I just had my first ever CTD right now on the loading page after clicking fly now 
Edit: second CTD while trying to switch cameras to exterior view
Okay this isn’t good anymore. 4th CTD of the day within 10 minutes.
Any ideas?
1 Like
XMP not stable for MSFS
You said there were two profiles - try the second one to see if that helps any
It’s exactly what I had back in August. MSFS is very sensitive to any instability in memory (DRAM & VRAM).
What I did: manually tuned the timing and increased voltage. You can copy the XMP timings and sub-timings and bump the voltage from default 1.35 to 1.4 - 1.45. Or underclock the timing if you are good at it.
Okay that fixed the issue. Geez! I started to panic!
Yeah that’s exactly what I did. Turned off dev mode and just went with it. I think the more we stare at those numbers, the more we mess around with the whole pc in general then we end up breaking something. I’ll just wait for a better optimization on the sim and hopefully once we get DX12 it can perform better like it’s meant to be especially with high end PCs
I’m taking your advice. I stopped chasing those frame numbers. Now I’m just enjoy the sim and hopefully one day it gets optimized.
Yooo you’re absolutely right! MSFS is not XMP stable. I experienced 5 CTD’s today by switching to XMP-I and XMP-II.
Went back into bios and reverted the settings back to AUTO and didn’t suffer any CTD after that.
Unfortunately I guess I can’t use the whole 3600mhz of ram and I have to stick to 2133mhzz
2133mhz is really underclocked for your processor. Base frequency is 2933mhz. You should really look to resolve that. You can manually enter in your timings which as already mentioned by another user are printed on a sticker on the memory sticks. You will still need to enable an XMP profile but then go in and change the CAS latency timings to what is printed on the memory, then save and exit the BIOS. It could likely be the XMP profiles are inputting incorrect CAS latency values and that indeed will cause instability and crashes. Either way, don’t just settle on leaving it at 2133mhz as you’d be doing the machine a disservice.
Is there any guidance on how to do all that? I’m not really a computer genius and I really can’t afford to break something