I’m wondering why no one on the overclock forum asked about the memory model and A-die or M-die? This detail is crucial because certain timing values won’t work with M-die while they should be fine with A-die.
That’s a good point. I’ll pan around in a NYC flight (sky, ground) and see how that number varies in both scenarios (cap on, cap off.) Then do the same over the Sahara.
The dance.
I’m puzzled by that as well. It’s obvious that over the Sahara capped at 60 FPS, the Main Thread latency is much lower (7ms vs. 13ms.) But GPU latency increases from 13ms to 17ms, leading to around 30% higher overall latency than when it’s uncapped.
I agree 100%. But low latency is important, don’t you think? The question is, does balanced Main Thread/GPU latency matter more than the lowest possible Main Thread latency? I’ve always sought the latter.
The 1% Lows were much improved in the uncapped scenario.
That’s the next step. I’ve been doing these tests with minimal addons (FSUIPC and Better Bravo Lights are active.) I’m going to start adding on my usual, one at a time - including REX and all the MAMU - and continue testing.
Either way, it’s very encouraging that I should even consider capping framerate with PG on, traffic @ 50%, and LOD set to 205/145. I’m seeing almost no ‘object popping’ anymore. And that’s huge. Because it was horrible before.
But I do think it’s easy to get lost in these numbers and chasing them. I’m not even sure how they relate to each other. What is most important to me by far is how it FEELS when flying. That is all that matters really.
I don’t know about the 0.1% lows etc. I don’t really have low FRAME RATE ever, I just get the hitching. Which is nothing to do with the general health and balance of the CPU vs GPU I think. It’s just JANK flightsim code and the way mods integrate into the ecosystem (…badly).
I have also spent many months (actually let’s just call it a few years by now) tweaking and testing, and although not scientific as your approach, I got a good feel for it within what I can understand. What I have now is as good as I can get it, short of potentially a Windows reformat and reinstall everything which I just have not got the energy for!
Side-note - my hunch about Mamu Powerlines seems to have been correct. Unticked JUST that (leaving this many mods active still, plus some background apps)…
…and so far it has really smoothed out the Triple-S’s (so maybe it was a case of MADness and UPS all along? ) .
1% lows (I think) has a lot to do with the variability of the data that we see as ‘smoothness.’ You can have 60 FPS average, but if 1% of your framerate is 20 FPS, you may see stuttering. In all the videos I see, that gaming metric seems to be mentioned as mucho importante.
You should download CapFrameX and capture a few flights. It’s very illuminating.
Not happening for a few years at least, my friend.
I’m a one-and-a-half-generations behind the times kind of guy.
When the sim first became available for pre-sale, a lot of folks recommended that I not build AM4, and wait a few months for the first AM5 parts. My 5800X3D worked well for a couple of years, but it’s showing its age. My 3090 Ti is doing OK as well, but its days are numbered, for sure.
Probably 6 months to a year before I upgrade the GPU.
CPU is good for a while.
The ‘Storm’ preset is wild. Lots of lightning, and if I didn’t know any better I would swear I was flying through some serious updrafts and downdrafts. At one point I flew into a storm cloud with heavy rain under it. I started overspeeding and losing altitude FAST. Had to disable AP, throttle way back, and pull the yoke to level the plane. Then I suddenly started gaining altitude like crazy and had to push the yoke almost to the forward limit and push the throttle/prop levers to the firewall.