So with 2020 we had cache being king.
With 2024 it looks like we have a dual-kingship, cache AND clock speed are king.  That's a big plus for both Intel and AMD users.  To me it indicates a major difference under-the-hood between MSFS2020 and MSFS2024.   It's not JUST the multicore differences which have been well-documented in forums like this one, but it's the response to clock changes that's also been improved in MSFS2024, if your testing holds true in multiple configs and multiple sim-situations. 

On 3/25/2025 at 10:18 PM, V1ROTA7E said:

My CPU tops out at around 67C with the absolute highest being 71C. This is with the +200 boost enabled. 

I upgraded my cooler and with a 100mHz increase runs at around 72-74 now in demanding scenarios in-sim.  But my question to you is, with the +200 boost what are you seeing on CPU core voltage when say running a stress test with all cores as setup for sim use? And, in-sims, what do you see for CPU core voltage?

3 hours ago, Noel said:

I upgraded my cooler and with a 100mHz increase runs at around 72-74 now in demanding scenarios in-sim.  But my question to you is, with the +200 boost what are you seeing on CPU core voltage when say running a stress test with all cores as setup for sim use? And, in-sims, what do you see for CPU core voltage?

The 200 boost is simply allowing the cpu to boost if conditions are safe to do so. The highest voltage I’ve seen in the sim was 1.32 I believe. I’ll check again when I get home and report back. 

11 hours ago, V1ROTA7E said:

The 200 boost is simply allowing the cpu to boost if conditions are safe to do so. The highest voltage I’ve seen in the sim was 1.32 I believe. I’ll check again when I get home and report back. 

Thanks for the reply yes check it out fully--a glance now and again won't capture too much.  Ryzen Master will capture current and peak.  AMD is clear that the X3D cache memory is particularly vulnerable to higher voltage and says to stay under 1.35v.  I can easily run +200mHz but Vcore hovers around 1.33-1.34v and witnessed a few transients to 1.38, 1.36, etc w/ my chip which is too close for my comfort.   Also noticed in Ryzen Master was seeing watts approaching 160 on this 120W rated CPU with that particular overclock.

Using Ryzen Master and Process Lasso I am super happy with my level of OC now and I am using Limit by Motherboard, currently mHz only inc by only 50 and with that core voltage stays right a 1.28 so can bump up that up to 75mHz next boot and see.  Curve Opt is set by CCD, with CCD0 at -30, CCD1 at -15 and ultra stable, and temps are way cool now, under 70C with the new cooler in MSFS 2020 right now in the PMDG 738 out of KSAN.  My OC goal is to stay around 1.30v +/- a few hundredths.  With PL I am running both sims on CCD0 and all other active processes on CCD1 seems to work great.  So sweet to be back away from Frame Generation, though there will be spots I will use it.  I asked Reset XPDR if he could possibly access control to be able to toggle FG on and off during runtime which would be fabulous but he gave a answer as to why he didn't want to try that and believes very few users would care anyway.

Edited March 30, 20251 yr by Noel

5 hours ago, Noel said:

Thanks for the reply yes check it out fully--a glance now and again won't capture too much.  Ryzen Master will capture current and peak.  AMD is clear that the X3D cache memory is particularly vulnerable to higher voltage and says to stay under 1.35v.  I can easily run +200mHz but Vcore hovers around 1.33-1.34v and witnessed a few transients to 1.38, 1.36, etc w/ my chip which is too close for my comfort.   Also noticed in Ryzen Master was seeing watts approaching 160 on this 120W rated CPU with that particular overclock.

Using Ryzen Master and Process Lasso I am super happy with my level of OC now and I am using Limit by Motherboard, currently mHz only inc by only 50 and with that core voltage stays right a 1.28 so can bump up that up to 75mHz next boot and see.  Curve Opt is set by CCD, with CCD0 at -30, CCD1 at -15 and ultra stable, and temps are way cool now, under 70C with the new cooler in MSFS 2020 right now in the PMDG 738 out of KSAN.  My OC goal is to stay around 1.30v +/- a few hundredths.  With PL I am running both sims on CCD0 and all other active processes on CCD1 seems to work great.  So sweet to be back away from Frame Generation, though there will be spots I will use it.  I asked Reset XPDR if he could possibly access control to be able to toggle FG on and off during runtime which would be fabulous but he gave a answer as to why he didn't want to try that and believes very few users would care anyway.

Just loaded up a quick flight at LFMN in the iniA320 in FS24, maxed everything. Voltage is averaging 1.33-1.38. I haven't heard about the AMD recommendation...But, honestly I'm not all that worried about it. Temps are well within limits, at the time of checking the CPU temp was at 57. Side note, i was lucky enough to also get a 5090, and while using 4x frame gen (i know you hate frame gen, but hear me out) it's been mind blowing. The 99 series chips provide such a solid and consistent frame time variance that even using 4x frame gen, there is very very very little artifacting. If you're happy with the OC you have, no reason to shoot for more, especially if you're going to use AutoFPS. At this point, it's really overkill.

2 minutes ago, V1ROTA7E said:

Just loaded up a quick flight at LFMN in the iniA320 in FS24, maxed everything. Voltage is averaging 1.33-1.38. I haven't heard about the AMD recommendation...But, honestly I'm not all that worried about it. Temps are well within limits, at the time of checking the CPU temp was at 57. Side note, i was lucky enough to also get a 5090, and while using 4x frame gen (i know you hate frame gen, but hear me out) it's been mind blowing. The 99 series chips provide such a solid and consistent frame time variance that even using 4x frame gen, there is very very very little artifacting. If you're happy with the OC you have, no reason to shoot for more, especially if you're going to use AutoFPS. At this point, it's really overkill.

I made the comment when 5090 first came out, that 4x or 8x FG *should* obscure FG related artifacts.  Do you use a 2nd display as I do?  I'm frequently going back and forth and that is another source of frequent image stability disruption.  I'm super happy with even a rate of 50FPS it's amply good when there is literally zero artifact of any kind.  Since I can change the frame lock with key presses I can easily bump that up to 70FPS-na in the air, but it's just not worth the effort, the finger-pressing effort 😉 so I don't bother.  Would I take rate of 200FPS-fg that obscured all artifacts including the 2nd screen judder issue, sure!   But I'm back to Nirvana land once again.  I do use DynamicLOD Reset albeit modestly.  The 9900X3D is tuned to perfection and longevity now, temps are crazy good too, often below 70C now.  I am of the camp that believes its voltage exposure more than heat that will do in the CPU.  From the oracle:

AMD officially recommends keeping the core voltage (Vcore) on the Ryzen 9 9900X3D at or below 1.35V for safe, long-term operation. For 3D V-Cache models, including the 9900X3D, AMD has stricter voltage guidelines compared to regular Ryzen CPUs due to the sensitivity of the cache layers.

✅ Official AMD guidance:

• Maximum safe Vcore: 1.35V

• Recommended daily use: ≤1.3V

• V-Cache limit: AMD specifically warns against exceeding 1.35V, as higher voltages can potentially damage the cache or reduce its lifespan.

• Key takeaway: Overvolting is potentially more damaging than higher (but in-spec) temps, especially for V-Cache CPUs.

12 minutes ago, Noel said:

AMD officially recommends keeping the core voltage (Vcore) on the Ryzen 9 9900X3D at or below 1.35V for safe, long-term operation. For 3D V-Cache models, including the 9900X3D, AMD has stricter voltage guidelines compared to regular Ryzen CPUs due to the sensitivity of the cache layers.

✅ Official AMD guidance:

• Maximum safe Vcore: 1.35V

• Recommended daily use: ≤1.3V

• V-Cache limit: AMD specifically warns against exceeding 1.35V, as higher voltages can potentially damage the cache or reduce its lifespan.

• Key takeaway: Overvolting is potentially more damaging than higher (but in-spec) temps, especially for V-Cache CPUs.

I consulted the overlord as well, and it's saying that it's totally fine, and shouldn't dramatically reduce life. Temperature is key and is "the #1 killer," its words, not mine lol. It did say that long term wear from high voltage is possible, but modern CPUs (with good cooling and power delivery) are made to handle these ranges. If it can last 2 years, I'll be happy since new stuff will probably be out by then anyway. I tend to replace my system every 2 years or so, so it's not a huge issue, personally. I can totally understand if you want to keep using your system for the next 5-7 years....then yeah, taking a more conservative approach makes sense.

32 minutes ago, V1ROTA7E said:

I consulted the overlord as well, and it's saying that it's totally fine, and shouldn't dramatically reduce life. Temperature is key and is "the #1 killer," its words, not mine lol. It did say that long term wear from high voltage is possible, but modern CPUs (with good cooling and power delivery) are made to handle these ranges. If it can last 2 years, I'll be happy since new stuff will probably be out by then anyway. I tend to replace my system every 2 years or so, so it's not a huge issue, personally. I can totally understand if you want to keep using your system for the next 5-7 years....then yeah, taking a more conservative approach makes sense.

Yeah but did your overload read absolutely everything ever written online anywhere, mine did 🤣.  Sure I get it for you.  I'm generally conservative by nature with everything I do I like to get value and useful service life and those last few volts just hardly deliver anything as I see it.  +75mHz is the sweet spot it turns out for this system and beyond it just adds 2.3% more potential increase in thruput, or for my baseline of 50FPS-na means about 1FPS difference, IOW, not noticeable.  And that 50FPS-na is with TAA so no need for smearing GC characters either.  I notice when I tried your suggestion of DLSS4 Performance the open frame rate went up some for sure.  My typical build has been every ~4y so this build I will likely hold for another 3y.  That being hoped, I've yet to run super demanding planes in 2024 so we'll see when that happens but I have to think it will go well as it currently is in MSFS 2020 with the same configuration. 

Tell us more about 200FPS-artifact free!  What about the 2nd screen issue?

47 minutes ago, Noel said:

Tell us more about 200FPS-artifact free!  What about the 2nd screen issue?

I don't use a second screen...yet. The FG at 4x is actually quite remarkable. The most stressful test was KLAX in 2020 with BATC running traffic injection in the 777 and TLOD at 400. Native FPS were probably in the neighborhood of 22-23, but with frame gen it was over 80. That 80 FPS didn't really "feel" like 80, to be honest. It felt more like 40...but that is subjective. It did definitely make a difference though, and was playable without issues. No stuttering or weird warping like with LSFG. There was some artirfacting in in the N1 fan blades, but i guess that's to be expected. Overall, interesting to say the least, and useful in ridiculous situations. In real life, I'd run AutoFPS or something, and keep things more reasonable, though. This was all just for testing. I'm also using Gsync, so FPS with Vsync is capped to 165...I didn't try unlocked yet. Surprisingly though, in some situations, the GPU actually maxes out...just a small reminder of how solid these new CPUs are.

Well enjoy that 5090 it doesn't get any better for sure!

I have been whining about the issues w/ FG and never used it at all after upgrading to 4090 because of the artifacts.  That all came from historical precedent of having that rock solid image stability and zero ghosted/smeared characters and no alternating screens focus judder for ages--but at a low framerate of ~35FPS-na.  Not that long ago to have maximum image quality 35FPS was about it, especially w/ that unreal low frame time variance that correlates to the perception of smoothest animation possible at that rate:


When I got the 4090 to use some of its horsepower I upped PrimaryScaling to 1.5 which really sharpened edges in the distance along with doubled VRAM made the upgrade worth it from 3080Ti.  I tried my hardest to accept the FG artifacts but it was always a challenge for me.  I would start a flight in FG, then abort shortly into taxi w/ the heinous strobe/flicker, made worse by my other settings.  Finally caved in and used FG for quite a while and put up with the 2nd screen issue and other artifact, using DLSS4 to cope, but then the ghost/smearing etc. 

So now back to full blown Nirvana, once again but now at 50FPS-native.  What still matters:  50FPS-na (or any lock) with at least 10% headroom over it delivers bigtime when all else is as good as it gets.  Panning is wonderful.  Maybe someday NV will somehow get around the resume focus issue w/ multiple displays--apparent Lossless Scaling does I read here I think. 

Right now the only performance issue in 2024 I get is while taxiing in a scenery complex airports I will get an occasional 'shudder', I don't know what else to call it, and I think it must have to do with loading scenery.  It's like a short-lived cluster of micro-stutters lasting less than a second.  I'm thinking maybe this has to do w/ the rolling cache which I have set at 32Gb, but I'm now flying all over in 2024 so maybe I need a bigger one? 

1 hour ago, Noel said:

Right now the only performance issue in 2024 I get is while taxiing in a scenery complex airports I will get an occasional 'shudder', I don't know what else to call it, and I think it must have to do with loading scenery.  It's like a short-lived cluster of micro-stutters lasting less than a second.  I'm thinking maybe this has to do w/ the rolling cache which I have set at 32Gb, but I'm now flying all over in 2024 so maybe I need a bigger one? 

I've read somewhere that 150GB is the sweet spot for rolling cache. I'm not thrilled that it's mandatory in 2024, but haven't had many perf problems so far. Like you said though, not many super high fidelity planes in the sim yet. The real reason for the 5090 was because of the VRAM, the other stuff is a bonus lol. It's wild, at ini airports, i've seen it reach 28GB....that seems obscene lol. But I know what you're talking about with the "shudder" while at large airports. ini takes the cake again...it's usually those airports, specifically, that has that issue.

One thing I have done in 2020 and forgot to try in 2024 is pre-load the scenery surrounding the airport during pre-flight by opening up the drone cam and heading up a few thousand feet then hold down the two keys that rotate horizontally and vertically at the same time for a few seconds then on down to the ground ending with the reset key which is numpad 5 in 2020.  I think it helped in 2020 so I will try it in 2024 now and will increase the rolling cache too thanks.

On 3/21/2025 at 12:48 PM, Mace said:

I feel like Chief Ten Bears in "The Outlaw Josey Wales" -- "....all of these things you say we will have....we already have..."

😀

Being, smoothness.   I sit back and observe these things closely, so I appreciate the info.  My only immediate move will probably be to go to 64GB of ram.  I would imagine if the sticks are on the QVL for my board I should be good-to-go if I decide to upgrade to a 9xxxx3D.   I keep telling myself I won't do it, but...it's hard to resist.

64GB was a game changer for me.  2024 constantly exceeds 32GB with addons.

23 hours ago, ryanbatc said:

64GB was a game changer for me.  2024 constantly exceeds 32GB with addons.

I noticed that the other day, I was capping out my ram, and it was disturbing!!  lol.  Time to go 64.  I bet I don't know what I'm missing.

39 minutes ago, Mace said:

I noticed that the other day, I was capping out my ram, and it was disturbing!!  lol.  Time to go 64.  I bet I don't know what I'm missing.

IF you fly native 2024 with just stock its fine... but what I think happens is all the 2020 addons aren't setup for 2024 and they just destroy performance.

Especially vram - as native 2024 addons use a different file extension for textures now.