First let me say, prior to SU2 MSFS2024 was working great for me. The sim was smooth, looked good and I hadn't run into any issues and no freezes or CTD's.

Post SU2 my controller interface is delayed anytime I want to make control adjustments. Planes keep loosing there programed controllers. Settings keep getting reset every few boots, especially Assistance. And I'm seeing occasional freezes and CTD when clicking on the camera icon. I know why but I wish we had an option to not update until were ready to do so for this very reason. I'm seeing from post that SU3 seems to be addressing some of these issue. I'm not big on using betas so I'll have to wait on SU3. 

For now I still use MSFS2020 which has been flawless.   

18 minutes ago, Wise87 said:

First let me say, prior to SU2 MSFS2024 was working great for me. The sim was smooth, looked good and I hadn't run into any issues and no freezes or CTD's.

Post SU2 my controller interface is delayed anytime I want to make control adjustments. Planes keep loosing there programed controllers. Settings keep getting reset every few boots, especially Assistance. And I'm seeing occasional freezes and CTD when clicking on the camera icon. I know why but I wish we had an option to not update until were ready to do so for this very reason. I'm seeing from post that SU3 seems to be addressing some of these issue. I'm not big on using betas so I'll have to wait on SU3. 

For now I still use MSFS2020 which has been flawless.   

I also want to share this information that resolved my issue, hoping it will be helpful to others. I believe the problem is related to corruption in the cloud settings. Unfortunately, you will need to start from  0 with your peripherals, and every new/adjusted setting you need to "Save and back". For now, before ASOBO breaks something else, my settings are saved correctly and hold. I really don't understand how it is possible for ASOBO to have the most critical/core function, "flight control settings," in a "flight simulator" to be such a disaster. 

 

For Steam Users:

1. Go to your Steam Library.
2. Right-click on "Microsoft Flight Simulator 2024".
3. Select "Properties".
4. Uncheck the box that says "Keep game saves in the Steam Cloud for Microsoft Flight Simulator".

To completely remove any cloud-saved data:

1. Open File Explorer and go to the following directory: C:\Program Files (x86)\Steam\userdata\
2. Find the folder corresponding to your Steam profile ID (it will be a number).
3. Inside that folder, delete the folder named 2537590.
4. Restart Microsoft Flight Simulator 2024. You might see the initial onboarding screens again. Launch a flight.
5. If everything works as expected, you can close the game and re-enable Steam Cloud Sync in the Properties if you wish to use it again in the future (though this would then start syncing again).

For Microsoft Store/Xbox App Users:

There isn't a direct option to disable Cloud Sync. However, you can delete the cloud save data. Be aware that this action will permanently erase your logbook, custom control profiles, and settings. Achievements already unlocked will remain, but progress towards new ones and logbook data will be lost.

To delete your cloud save:

1. Close Microsoft Flight Simulator 2024.
2. Open Command Prompt. You can do this by typing "CMD" in the search box and selecting "Open".
3. In the Command Prompt window, copy and paste the following command:

   start shell:appsFolder\Microsoft.Limitless_8wekyb3d8bbwe!App -DeleteCloudSaves
   

4. Press Enter.

This command will initiate the deletion of your cloud saves for MSFS2024.

Keep in mind that disabling or deleting cloud saves might prevent your settings and progress from being synchronized across different devices.

Thanks for the info. I have read about the procedures you mentioned above. It's the part about having to start from scratch that scares me the most. The fact that it took me some time to figure out how to use the new 2024 controller menu options and after months of tinkering, have finally gotten my controls configured the way I like it. To start from scratch would be painful. Too bad we have no option to save to local drive and then flush the cloud. I have resorted to the old school ways of saving my settings by taking screenshots of every section. Controllers are a little more difficult and I wish we had an export option. 

Edited May 22, 20251 yr by Wise87

1 hour ago, Wise87 said:

The fact that it took me some time to figure out how to use the new 2024 controller menu options and after months of tinkering, have finally gotten my controls configured the way I like it. To start from scratch would be painful

You’re a perfect example of what I just mentioned in another thread and I completely agree with you.

 

So much of this annoying stuff that became broken in the SU2 beta was reported, but they went ahead and released it anyway... Will they ever learn?

3 minutes ago, abennett said:

So much of this annoying stuff that became broken in the SU2 beta was reported, but they went ahead and released it anyway... Will they ever learn?

Asobo doesn't seem to pay much attention to beta testers' input. 

32 minutes ago, Bobsk8 said:

Asobo doesn't seem to pay much attention to beta testers' input. 

No, it’s utterly pointless.

The simple answer to all of this is that the devs have just taken too much on. It’s become too big a project for them to cope with and they’ve completely lost control of what’s going on. Regressions being introduced left, right, and centre. Regressions from 2020 to 2024, from sim update to the next sim update. It’s the same with some aircraft developers, they rush things out and just break a load of stuff and add fancy vanity new features, when the core product still does not work properly.

Edited May 22, 20251 yr by abennett

I am having similar issues since SU2, particularly the regular reset of my settings. I am not quite ready to nuke my online profile yet, but it is not far off and I hope that corrects the issue. 

I was surprised by Seb's statement in the "Dev Stream that they thought they fixed everything with the control settings but let us know if there is still some issues." I enjoy 2024, but there are certainly some frustrating aspects to it.

That's what I'm talking about, this is total chaos development. There are no controls over anything. There's no quality control. Zilch! Random Devs breaking random stuff, daily! The only competent ones are Working Title.

25 minutes ago, Greazer said:

That's what I'm talking about, this is total chaos development. There are no controls over anything. There's no quality control. Zilch! Random Devs breaking random stuff, daily! The only competent ones are Working Title.

That's funny, I just completed a 1400-mile PMDG 777F flight from Memphis to LAX. And my controls and flight were perfect to touch down. My controller settings have never been erased or altered. I also keep a copy of my user.cfg on another drive just in case.

2 minutes ago, Bigmack said:

hat's funny, I just completed a 1400-mile PMDG 777F

Yea, I think we need to be thoughtful in the conclusions we draw. I am having an issue with my settings being reset from time to time, but, I am also about to finish 2,300 nautical mile flight from Toronto into Anchorage in the 777F accompanied by BATC and the experience has been engaging and immersive, smooth, weather matched all along the route; a very enjoyable experience.

I haven't figure it out but within the same aircraft different livery treated as different airframe. For example, if I assigned my controls to PMDG 777 American Airlines liver and then next time decided to fly same airplane by in Delta livery,  controls assignments for Delta livery will revert to default. All need to is to reassign my saved two engine jet profile to Delta livery . 

Yes it's little bit annoying but not a big deal because  right after 2024 was launched  I have spent few days creating and saving profiles for all kind of aircraft: prop, jets, two engine, four engine and so on. Those profiles stay intact from day one and never got erased. All I need to do is to assign them to particular livery next time

It’s somewhat funny that we’ve kinda gone full circle, P3D/FSX has 3rd party tools to manage controls and now it seems we need them for MSFS 2024.

36 minutes ago, sd_flyer said:

I haven't figure it out but within the same aircraft different livery treated as different airframe. For example, if I assigned my controls to PMDG 777 American Airlines liver and then next time decided to fly same airplane by in Delta livery,  controls assignments for Delta livery will revert to default. All need to is to reassign my saved two engine jet profile to Delta livery . 

Yes it's little bit annoying but not a big deal because  right after 2024 was launched  I have spent few days creating and saving profiles for all kind of aircraft: prop, jets, two engine, four engine and so on. Those profiles stay intact from day one and never got erased. All I need to do is to assign them to particular livery next time

I setup my Velicity Flight stick one time for all my basic functions landing gear, flaps, Auto throttle and my rudder controls on my CH pedals. And I setup as default across all aircraft and I only have to change some things depending on whether I'm flying a prop, Helo or tubeliner. I mostly I never have to touch my controller settings going from aircraft to aircraft.

Edited May 22, 20251 yr by Bigmack

53 minutes ago, Bigmack said:

That's funny, I just completed a 1400-mile PMDG 777F flight from Memphis to LAX. And my controls and flight were perfect to touch down. 

Flight control while in a flight is not the issue. Its the part where they keep resetting or the long delay to access the control menu that bites.