What happens? You described what you tried, but not what you were trying to fix.
1 Like
GPU utilization drops at around FL250/FL270 and above, which decreases my fps from 70-60 to 30.
and this you would fix with these NDU stuff , which was a memory leak ? Thats may be the power of the word āAMAZINGā in heading 
We have better topics related to these kind of issues:
as example:
GPU utilisation drops likely because there is not much to draw at FL270. Your plane, and the sky pretty much. You are so high that the ground buildings have most likely been culled out of existence.
Yeah true but why would it drop fps so dramatically, moving in the cockpit is a real bother now. Besides it wasnāt happening before.
That may not be related to GPU utilisation, but you have inferred this because you saw low GPU utilisation.
What you could do is repeat the test. Relaunch the sim, check the GPU utilisation, and frame rate while on the ground, then slew straight up to FL270, or thereabouts, then compare those same readings.
I REALLY wanted to get this up yesterday, but the site was read-only for some reason. Thereās a fix, gents and ladies, and thereās actual science and testing on it. The link to the video is below. If you follow Overkill on YT, youāve already seen it over the last few days. I hesitated to post until I gave it 100 hours in the most stressful of places, performance-wise, on the globe. Itās legit. No more leaks. ZERO. Itās NVIDIA bloatware thatās hurting us. Surprise, surprise! Load up at JFK and be amazedā¦
3 Likes
To save those the time with questions, the process is a complete wipe of video drivers and anything NVIDIA. Then, you create a custom driver, less the extra bloat via NVIDIA(youād be surprised the nonsense in the full driver), and you use that. BAM. Butter smooth sim.
1 Like
I did this and had numerous blue screens after the fact. Iāve reinstalled the full driver, minus GeForce experience after a ddu of the nvclean driver I created and so far no blue screens.
More flights needed before I can say with confidence that the ābloatfreeā driver was causing the bsod Tho. Just something to keep I mind Incase anyone tries this and gets bsods when loading flights or even mid flight sometimes.
For those with gaming laptops and rely on Optimus, even though itās installed as part of the video instructions, Optimus no longer works for me with this setup.
I did try a flight with this setup and even though Iām usually CPU limited, I did measure 4 FPS improvement with noticeable smoothness. This is with same plane at KLAX with clear skies and 10am local.
Reinstalling the nvidia driver without GeForce restored properly working Optimus.
Very interesting. Iāve had nothing but positive results. I was skeptical at first because Iām far from a PC expert, but I just followed it step by step and it worked. I figured if it didnāt, I could always go back to what I had before.
Rest assured if my bsods continue Iāll probably give this skinny driver another shot (once I establish the root cause) because performance did SEEM better but thatās my anacdotal take.
Bsod after about an hour in the a320 FBW after a reinstall of the full driver.
Which version of the FBW are you using?
Is it current?
Experimental.
HOWEVER. I debugged my minidump file and did some googling and Microsoft said my specific error code was hardware failure, heat, bad overclock and NOT driver related.
Took my overclock out and so far, after a few flights. No BSOD yet.
Iām going to assume that was the cause. I will give the skinny driver another shot once Iām confident my BSODās are resolved.
MSFS can be quite fussy with overclocks.
2 Likes
I have the exact same results. In my case I slightly reduced my o/c and have now been rock solid for a month. CTDs are pesky little buggers. Glad you found a solution.
Good to know. I thought about reducing it but its been in place so long i forgot what all i had to tweak in my BIOS so i just loaded the optimized defaults and ran with it. The OC has been in place for over a year at least with no issues. Then all of a sudden BSOD every flight. Hopefully i didnt shorten the life of my CPU TOO much!
The sim notoriously hates OCs. Itās been a problem since the outset.
Tried all the magic bullet tips & tricks back in FSX, P3D and for good measure in FS2020 as well. Including this one. No difference whatsoever.
The only thing that made a difference was throwing an RTX 3060 Ti at the whole thing, replacing my GTX 1070. That gave me a considerable boost with more situations hitting 50 to 60 fps as opposed to 35 to 40 fps.
I can imagine that a tweak sometimes DOES work, but only if something was seriously misconfigured or screwed previously and got fixed by the tweak. But if your system was well maintained before, it wonāt do anything ā¦
1 Like
I wrote this a couple of days ago, but couldnāt post it (read-only mode), so I saved it to post later,
I followed the tutorial, and gained nothing. Also, a lot of people give advise without caring about the other personās preferences. He said to disable everything to do with GeForce experience, and totally disregarded those who like to record their simming with ShadowPlay, etc. The only thing that worked for me was reducing my Terrain LOD from 200 to 150, and that only on few airports like the new KBOS. For some reason that airport is CPU intensive, so although I have a huge GPU headroom, my i9-9900K @ 5GHz canāt handle it. Yet EBBR runs like butter, and my GPU (EVGA RTX2080Ti FTW3) is the bottleneck. Iām about to reinstall my Geforce Experience because for some reason Iām not able to record Star Citizen with OBS Studio, so I use ShadowPlay.
They give instructions as though you built your $3,000-$5,000 rig just for MSFS. Itās not one size fits all. As good and wonderful as MSFS is, itās not the only thing on peopleās PCs. So annoying! And a lot of people claim how it gave them 1000% increase! Iām not saying theyāre intentionally lying but people tend to exaggerate.
Having said this, I have to admit that for the first time in what seems like ages, I was able to do a 7-hour flight (KBOS-EBBR) and the framerate did not drop. I locked it at 30 FPS and it remained there till the very end, and my landing was even so much better (see pic), but also, my MSFS got reinstalled by itself. Looks like because I didnāt exit the beta manually, it forced me to do a 121.77GB update, which is pretty much the whole thing, and I had to reinstall every world update too. So I donāt know what fixed the FPS degradation for me. Also, I still have the NDU fix enabled. So a multiple of things could have taken care of it, I donāt know, and Iām too tired to verify right now, but Iām gonna fly another long-distant trip to confirm
