Just something to be aware of, that I certainly was not aware of.

Background

I've just upgraded to an AMD9800x3D and have been running the Ryzen Master software to check the temperatures and the individual core usage when running MSFS2020 and MSFS2024

General Observations

The Ryzen Master software gives all sorts of info, but I was looking particularly at temperatures (good for both sims in all stages) and core speeds (the chip is rated to boost to 5200 GHz)

The two sims, when running the same 2D takeoff, circuit and landing routine had quite different core usages - MSFS2024 was using 3000ish to 4000ish GHz for pretty much all of the cores most of the time.

MSFS2020, on the other hand was generally running at those kinds of speed for a couple of cores and then much more like 1200-1500 GHz or less for the other cores

The 'should I be worried about this' surprise

I shut down MSFS2024 and the core speeds, predictably dropped to tickover

But when I shut down MSFS2020 - but before doing the Cntrl-Alt-Delete Task Manager routine to shut it down properly -  EVERY CORE WAS RUNNING AT THE MAXIMUM RATED SPEED (c5200GHz).  Every one of them.  As soon as I killed it in Task Master, all reverted to normal.

 

Personally, I'm not happy with any software that runs every core at max and so, until MS/Asobo fix this, I think am going to ALWAYS shut MSFS2020 with the Task Manager and not use Quit in the sim at all...

Is this a surprise to anyone else?  

3 minutes ago, AJZip2 said:

Just something to be aware of, that I certainly was not aware of.

Background

I've just upgraded to an AMD9800x3D and have been running the Ryzen Master software to check the temperatures and the individual core usage when running MSFS2020 and MSFS2024

General Observations

The Ryzen Master software gives all sorts of info, but I was looking particularly at temperatures (good for both sims in all stages) and core speeds (the chip is rated to boost to 5200 GHz)

The two sims, when running the same 2D takeoff, circuit and landing routine had quite different core usages - MSFS2024 was using 3000ish to 4000ish GHz for pretty much all of the cores most of the time.

MSFS2020, on the other hand was generally running at those kinds of speed for a couple of cores and then much more like 1200-1500 GHz or less for the other cores

The 'should I be worried about this' surprise

I shut down MSFS2024 and the core speeds, predictably dropped to tickover

But when I shut down MSFS2020 - but before doing the Cntrl-Alt-Delete Task Manager routine to shut it down properly -  EVERY CORE WAS RUNNING AT THE MAXIMUM RATED SPEED (c5200GHz).  Every one of them.  As soon as I killed it in Task Master, all reverted to normal.

 

Personally, I'm not happy with any software that runs every core at max and so, until MS/Asobo fix this, I think am going to ALWAYS shut MSFS2020 with the Task Manager and not use Quit in the sim at all...

Is this a surprise to anyone else?  

This was  talked about on the FS forum in many posts. I noticed right away that the CPU usage when MSFS was improperly shut down was at least 35%+. Not a good thing to be sitting there needlessly heating up my CPU for hours , Asobo should have fixed this yesterday. 

Edited May 16, 20251 yr by Bobsk8

9 minutes ago, Bobsk8 said:

This was  talked about on the FS forum in many posts. I noticed right away that the CPU usage when MSFS was improperly shut down was at least 35%+. Not a good thing to be sitting there needlessly heating up my CPU for hours , Asobo should have fixed this yesterday. 

Yes - but 35%+ is one thing, but 100% for all cores?? 

Anyway - I've posted a summary of the above on the FS Forum thread.  As it is a logged bug and that is the formal thread relating to it, hopefully there will be a bit more urgency put to it.  Frying my new 9800x3D on its first days outing isn't my idea of fun!

3 hours ago, LRBS said:

Thank you. 

Unfortunately, numerous issues are affecting this ASOBO software to the point where many customers wonder about the competence of the people involved in this project. There is always an issue with them. I wish they had a more stable product after so many years. It sounds to me like some other developer who is constantly blaming somebody else for their shortcomings. Unfortunately for ASOBO, I'm not the only one unhappy with their "progress."

The failure to fully shut down is just a minor issue for me - just a couple of clicks and it's sorted.  I don't understand the comment about the stability of MSFS2020.  I find it to be very stable and reliable, even with my 7 year old rig.  There's a part of me that says "Please don't touch it - it's fine as it is"!

I'm in no rush to go to MS2024 because of how good MSFS2020 is for me.  I can wait - may be after SU3 or 4 it would have settled down to be a mature product and some of the aircraft that I want to fly are only available in 2024.

12 hours ago, Farlis said:

Where have you been the last 5 years? There has always been a monthly Airac Update.

There may always have been an Airac Update but I was unaware of it as are notes supplied with each update outline what is included in the update?  Also without a paid subscription to Navigraph the FMC in the B738 displays that it is out of date. I don't understand. 

Also someone in another forum and/or thread once indicated that the Airac Cycle was only updated for MSFS2024 which I must say I thought strange.

 

Thanks also to those who have updated our knowledge of what is causing the problem. And it certainly is no good.

I remember this same problem occurring some time again which was eventually fixed and now its back.

19 minutes ago, Jarnie said:

Also without a paid subscription to Navigraph the FMC in the B738 displays that it is out of date. I don't understand. 

I assume you speak of the PMDG 738?

That one does not use the default database and as such needs to be updated externally.

But all default aircraft use the default database and that has always been updated monthly.

1 hour ago, Farlis said:

But all default aircraft use the default database and that has always been updated monthly.

Yes I meant the PMDG 738.

Thanks for sharing the knowledge.  I wonder why PMDG doesn't use the MSFS Airac.

 

Also a quick look at the GTN750 documentation suggests it too uses an internal 'version' of the Airac cycle?

 

 

Edited May 17, 20251 yr by Jarnie
add last sentence

7 hours ago, Jarnie said:

I wonder why PMDG doesn't use the MSFS Airac.

Many add on aircraft have their own database. 

The Aerosoft CRJ

The IniBuilds A350 (although that one can use both)

The IFfly 73Max

The Justflight RJ's

etc...

 

It is my understanding that it is the custom flight management systems that have certain functionalities that couldn't be simulated without their own database.

Whether that is still true though nowadays I'm not sure. Working Title did lots of improvements on that front in the base sim.

 

18 hours ago, Bobsk8 said:

This was  talked about on the FS forum in many posts. I noticed right away that the CPU usage when MSFS was improperly shut down was at least 35%+. Not a good thing to be sitting there needlessly heating up my CPU for hours , Asobo should have fixed this yesterday. 

its money.  its moving staff off over products and onto this,  which is time is time, resoucing and money. 

LM used to do the same old stuff. It if didnt benefit the military guys they didnt care no matter what rob and simbol made out.

20 hours ago, Peterwk said:

The failure to fully shut down is just a minor issue for me - just a couple of clicks and it's sorted.  I don't understand the comment about the stability of MSFS2020.  I find it to be very stable and reliable, even with my 7 year old rig.  There's a part of me that says "Please don't touch it - it's fine as it is"!

I'm in no rush to go to MS2024 because of how good MSFS2020 is for me.  I can wait - may be after SU3 or 4 it would have settled down to be a mature product and some of the aircraft that I want to fly are only available in 2024.

It's amazing how stable and reliable software can be when it can't be shut down properly and continues running in the background, yet it's considered "ok" or "just a minor issue." Let's be serious, please.

Ok so whats going on with 2020 just updated now i bet ctd on loading screen.

 

Also updated AIG

Now my oc folder is not recognized anymore as of its empty.but its not.

Just update driver to latest for my 5080.

Mike

14 minutes ago, mikeymike said:

Ok so whats going on with 2020 just updated now i bet ctd on loading screen.

 

Also updated AIG

Now my oc folder is not recognized anymore as of its empty.but its not.

Just update driver to latest for my 5080.

Mike

Try rolling back your driver to one that works. 

3 minutes ago, Bobsk8 said:

Try rolling back your driver to one that works. 

Thanks ill try that

1 hour ago, mikeymike said:

Also updated AIG

Now my oc folder is not recognized anymore as of its empty.but its not.

Assume you mean the OCI folder? Check that it does not have -beta at the end, if so - remove -beta. All explained at the AIG discord.

6 hours ago, fluffyflops said:

its money.  its moving staff off over products and onto this,  which is time is time, resoucing and money. 

LM used to do the same old stuff. It if didnt benefit the military guys they didnt care no matter what rob and simbol made out.

If this is indeed something in the MS Gaming Service app there may not be anything Asobo can do.  They may be dependant upon MS to provide the fix.  MSFS isn't the first game to hang shutting down because of gaming services...

Are Steam users not running gaming services or xbox app having the same issue?  

AI Overview

Learn more

 

If games aren't shutting down properly due to Microsoft Gaming Services, try uninstalling and reinstalling the service, or using the Gaming Services Repair Tool. You can also disable or reset the Xbox Game Bar, which may be interfering. If none of these steps work, you can also try updating Windows and your graphics drivers, or performing a clean boot of your PC. 

 

Detailed Steps:

1. 1. Uninstall and Reinstall Gaming Services:

   • Open Powershell as an administrator. 
      
   • Run the command: get-appxpackage Microsoft.GamingServices | remove-AppxPackage -allusers. 
      
   • Reinstall Gaming Services from the Microsoft Store. 
      
2. 2. Use the Gaming Services Repair Tool:

   • Launch the Xbox app for PC. 
      
   • Go to Profile > Support > Gaming Services Repair Tool. 
      
   • Start the troubleshooting tool. 
      
3. 3. Disable or Reset Xbox Game Bar:

   • Go to Settings > Games > Game Bar. 
      
   • Turn off "Use Game Bar to record game clips, screenshots, and broadcasts". 
      
   • Alternatively, reset the Game Bar: Go to Settings > Apps > Xbox Game Bar > Advanced options > Reset. 
      
4. 4. Update Windows and Drivers:

   • Check for Windows updates: Settings > Update & Security > Windows Update. 
      
   • Update your graphics drivers. 
      
5. 5. Perform a Clean Boot:

   • Search for "msconfig" in the Windows search bar and open it. 
      
   • Go to the Services tab and check "Hide all Microsoft services". 
      
   • Disable all other services. 
      
   • Go to the Startup tab and open Task Manager. 
      
   • Disable all non-Microsoft startup programs. 
      
   • Restart your computer. 
      
6. 6. Other Troubleshooting:

   • Check your antivirus settings. 
      
   • Close any associated game launchers that are running. 
      
   • Update and repair the game. 
      
   • Uninstall and reinstall the game.