3 hours ago, Cpt_Piett said:

I will not deny that I have a similar flaw

Your tests may have cured me of this. Thanks Doc!

47 minutes ago, Noel said:

Was this done with X3D Game Mode enabled in the BIOS?

No.

2 hours ago, rlashier said:

Thanks Captain Piett for this comparison. We now have objective findings based on data not subjective impressions. Safe to say that 2024 needs some work before it will be the equal or better to 2020 for performance. 

But can we say that with certainty, based on the results?   The FTV is better in 2024 and not to be dismissed so quickly as to FTV's effect on the sim, which might be outsized given the results of the seat-of-the-pants poll.   Some pretty interesting results Captain Piett.

Sure we can say it with certainty as to FPS, 1% lows, etc. with those aircraft, but if that's the case, how can so many people perceive 2024 as performing better?   Something else must be at play, whether it's FTV or just the shiny-new-thing effect going on, it's hard to say.  FTV we *know* is raw empirical data though.

34 minutes ago, Mace said:

But can we say that with certainty, based on the results?

I don't think it's a good idea to extrapolate too much based on my comparison. After all, it's only a very short flight in one of many default aircraft. And I partly agree in terms of FTV as IMO it's one of the best indicators of smoothness. However, the frame time spikes and stutters were far more severe in 2024 despite a slightly better FTV. Usually there's a good correlation between FTV and smoothness, but that wasn't the case with these tests. 

1 hour ago, Cpt_Piett said:

No.

In my now way too long quest to discover why I'm getting audio/video cutouts post update to 24H2 (am thinking that might be a red herring...) I updated the BIOS which brought in X3D Game Mode as an option.  FWIW which is almost nothing I did KSBA>KLAS this morning and nary a single stutter seen the entire flight right on into the arrival gate in the PMDG 738.  Zero audio/video cutouts, and THAT is very rare right now.  In fact, with no changes whatsoever am back up doing KOAK>KSBA and cutouts very early on and persisting I've notice already maybe 20 of these already and we're not even to cruise.  Freaking mystifying.  Anyway, this capture was done this AM from 35 minutes out from KLAS and was done w/ X3D Game Mode ON:

I think Game Mode on is not playing a role in this good FTV as I had this well before trying Game Mode. 

BTW I rarely ever see this very good FTV any more which is why I hit the capture key on this flight.  This is more like it when I have these freq audio/video cutouts as in the current flight.  By the time I post this I've had 50 of these hitches grrrrrr!!

I read there is a fix from MS coming having to do w/ audio issues post 24H2 we'll see...very frustrating, very random, one flight it's bad, the next flight completely better.  WEIRD~!

 

Edited December 30, 20241 yr by Noel

Worse for me. Lost 30% performance in VR...

28 minutes ago, Noel said:

I read there is a fix from MS coming having to do w/ audio issues post 24H2 we'll see...very frustrating, very random, one flight it's bad, the next flight completely better.  WEIRD~!

FYI -- in the Flysimware 414 in 2024, I have noticed zero audio issues in about 20 hours flight time.  It has worked perfectly.

But then I flew in the default CJ4 for a short (2 hour) trip and I had one incident of audio popping and cutting out about midway thru the flight.  It recovered, and was fine the rest of the way, but, I wanted to point out that audio problems might be airplane-specific.

My machine was recently updated to 24H2 also.  But all my Flysimware C414 flights have been under 24H2.

I've actually experienced audio issues as well, not sure if they are identical but just these brief 'clicks' that effects audio, like an audio stutter of sorts and does it periodically throughout the flight. Both times in the Fenix at cruise height, where it seems to be at its worst. I noticed in Process Lasso, the red responsiveness line does a small V dip every time it happens and CPU usage spikes a tiny bit for a second. So there's something in the rendering pipeline, background or the CPU scheduler process that causes a stall long enough to effect audio and effect responsiveness of the entire PC. 

Then when I'm on descend it disappears, been on long GA flights without out, so it's not consistent. 

Edited December 30, 20241 yr by Sethos

Just now, Mace said:

It recovered, and was fine the rest of the way, but, I wanted to point out that audio problems might be airplane-specific.

Thanks Rhett.  I use 5 diff planes and at least 4 of them are doing the same thing (haven't tried the 5th plane) so plane doesn't seem to be playing a role in this.  It kind of feels like a serious hardware fault somewhere. I've checked audio cables and DP cables, wiggled the 1/8th inch stereo plug jack thinking maybe it was defective, R&R audio/video drivers, chipset drivers all to latest from MSI's website for my board.   I even tested my 8 month old Corsair PSU which according to my tester failed to meet the PG signal range of 100-500ms, replaced the PSU,. to no avail.  At this point I hope the alleged acknowledgement by MS re audio issues and 24H2 actually provides a cure.  I believe whatever is causing this is worsened by high demand scenarios, though again flying into FT's KLAS was absolutely flawless in the PMDG 738 in terms of stutter and FTV this morning.  I don't think there is anything more I can do beyond wait and hope.

 

 

3 minutes ago, Sethos said:

I've actually experienced audio issues as well, not sure if they are identical but just these brief 'clicks' that effects audio, like an audio stutter of sorts and does it periodically throughout the flight. Both times in the Fenix at cruise height, where it seems to be at its worst. I noticed in Process Lasso, the red responsiveness line does a small V dip every time it happens and CPU usage spikes a tiny bit for a second. So there's something in the rendering pipeline, background or the CPU scheduler process that causes a stall long enough to effect audio and effect responsiveness of the entire PC. 

Then when I'm on descend it disappears, been on long GA flights without out, so it's not consistent. 

I can relate to some of this re when this happens.   Did you correlate this with 24H2 update?

11 minutes ago, Sethos said:

 Both times in the Fenix at cruise height, where it seems to be at its worst.

That's interesting, because in the CJ4 when it happened, I was at cruise altitude.  

I didn't have PL or any sort of monitoring running though.

I’m on 24H2 and have noticed audio issues in 2024 although not in 2020. Seems to correlate with hard stutters but not in all aircraft. Definitely in the Fenix.

6 minutes ago, Noel said:

I can relate to some of this re when this happens.   Did you correlate this with 24H2 update?

I did a clean install of Windows 11 just before 2024 released, which was a 24H2 install. So afraid I don't have any comparisons to anything before that update. I also didn't start noticing this until the past few days, as I've done quite a lot of flights over the holidays but at least I am aware now. For now I have only experienced it in the Fenix and only at cruise altitude. Thought it could be Fenix related but as Mace mentions, happens in other planes as well, so could be purely due to rendering stalls or maybe something funky with navigation, databases etc. stalling the entire thing, who knows. 

I've done some more tests to try to improve things with some success. I'm not going to post all the CFX screenshots here - but I'm getting better lows and FTV with SMT off. Then even better with PBO +200MHz and curve optimizer set to a negative 20 on CCD0. The difference is mainly related to less stutters (1% low avg increased from 41 to 53) - not a massive difference, but I guess it all adds up in the end. 

Not sure if all this tweaking is worth it, or sending me further down that rabbit hole. But it's a bit like overclocking I suppose - which I find enjoyable. I also like flying though, so there's a balance 🙂

Next: Updating the BIOS and test Gigabyte's X3D Turbo Mode. Hopefully it's a bit more advanced than just disabling CCD1 and SMT - but from the googling I've done so far, there's quite a bit of confusion as to what it actually does. 

Edited December 30, 20241 yr by Cpt_Piett

49 minutes ago, Cpt_Piett said:

Next: Updating the BIOS and test Gigabyte's X3D Turbo Mode. Hopefully it's a bit more advanced than just disabling CCD1 and SMT - but from the googling I've done so far, there's quite a bit of confusion as to what it actually does. 

This must be the same as X3D Game Mode for MSI's AMI BIOS.  I'm about to try the same perfect flight I did this AM KSBA>KLAS in the 738 with X3D GM off.