Search the Community

Greetings fellow simmers! There's no lack of discussion and opinions on how to improve stuff to get stellar performance in MSFS. Heck, I've been guilty of that too many times on this forum. I'd like to think that most of us to some extent are chasing that ever-elusive Holy Grail: excellent performance combined with excellent image quality. I'd also like to hope that not too many poor souls find themselves as deep down the rabbit hole as I do. Believe me, that hole goes very deep. A tell-tale sign of this chronic, deteriorating affliction is tampering with Nvidia profile inspector, registry editor, NDU and SysMain. Maybe I should have taken the blue pill? Contrary to my previous topic, I wanted to take the opportunity to try to wreck havoc on performance in order to identify where the worst bottlenecks can be found. Inspired by a fellow captain (who pleaded the 5th and begged me to maintain anonymity), I booted up the latest beta build at KJFK and threw the following at the poor sim: Inibuilds KJFK Fenix A320 V2 (as we all know the modelling of cockpit door opening makes it way more performance-heavy than PMDG 737) FSLTL AI Traffic (base and injector) AIG models, flight plans and injector (AIGTC) GSX Pro REX AccuSeason REX Airport Textures We Love VFR by PUF GAIST Ultra v4.0 with North American Caribbean routes enabled Seafront vessels core (I would have thrown in Samscene3D's New York City Times as well, but didn't feel like cashing out on it) It's worth noting that most of these apps will not treat the mainthread very gently. Well, that's an understatement, as we shall see. These addons don't enter the sim with silk gloves on. They come armed with sledgehammers. Sim settings: 5461x2880 || DLSS ultra quality || FG || DX12 || PG || Shadows 6144 || real weather + other settings ultra/max (except for glass cockpit refresh rate medium) I used AutoFPS in a desperate attempt to avoid my rig going down in flames. Situation: Fenix parked at gate, panel status ready, drone mode, no panning. FSLTL off: FSLTL on: AIGTC on at 100%: Without FSLTL: avg fps 71.9 smooth 100% FTV <2ms 99.2% With FSLTL: avg fps 70 smooth 100% FTV <2ms 92.53% With AIGTC: avg fps 50.9 smooth 99.8% FTV <2ms 65.11% There's a caveat here, and that is that this comparison doesn't do AIG much justice. I had fairly moderate FSLTL settings, besides at the time it was RW night-time in NY (I set MSFS time to noon though), and FSLTL uses "live" flight plans, vs AIG's offline. Also, to show how much of a heavy hitter max AI traffic can be, I chose to add AIG into the mix as it's easier to just set 100% traffic vs. FSLTL's more elaborate settings. In this pitiful scenario, there's simply no overhead left as the poor mainthread is working overtime. The 4090 won't save the day heroically in this case (which it normally tends to do - otherwise no one in their right mind would spend their hard-earned cash on it). Reset's brilliant app does it's absolute best but falls short as well. No hate whatsoever towards AutoFPS - it's absolutely brilliant and I use it with every flight. Otherwise my 12900KF would have melted long ago with my ridiculously high settings (which I would never have been able to use without AutoFPS). In case anyone was wondering: FG won't save the day either. In fact it'll make it worse. Like a blizzard-combined-with-11058G70KT-standing-at-BIRK's-tarmac-in-December-worse. Explanation will follow. With a still drone view above the airport, with most of the main terminals in view (packed with AI aircraft on the ground as well as in the sky, as far as the eye can see), the mainthread is red-glowing at 44ms (!), native fps 22 (!!) and FG-fps 45. I'm pretty sure I could both hear and smell the agony of the 12900's P-cores. Some brave ones were in fact coming dangerously close to TjMAX at 100 degrees celcius. Panning around makes things worse. Much worse in fact. It's what we would call a real stutter-fest. A real word-not-allowed-storm. The worst enemy of any Serious Simmer™. Not only does low native fps facilitate a catastrophically bad simming experience, but FG actually adds fuel to the fire. Nvidia recommends native 60 and above fps for optimal results. Here we've got feeble 22 native fps. This is an excellent example of the appearance of the dreaded FG-related flickering (which I like to call FG-inherent artifacts), and it's quite distracting. Well, distracting is an understatement. So we find ourselves in the perfect storm: absolutely horrendous stuttering-galore combined with FG-induced flickering-artifacts. The 4090 basically meets it's greatest nemesis in this scenario: a wrecked mainthread which is completely overworked, overwhelmed (and probably underpaid!). Perhaps the much praised 7800X3D would have saved the day? I might be going out on a limb here, but I'd venture to guess it wouldn't have. I challenge 7800X3D + 4090 owners to prove me wrong. Could we make it even worse? Well we could increase TLOD to 600 and OLOD to 1000 (it's possible, I've tried). But there's really no point in doing so, as we don't want to throw our Xbox controllers at our overpriced OLED panels. Well, that's it for now. Comments? Can we make it worse? Do we really want to? Is FSLabs better than Fenix? May the Force be with you all. Please don’t bother to get up, I’ll show myself out. Cpt signing off.