39 minutes ago, wthomas33065 said:

Look in the "fix" post in tips and tricks, it shows you how to identify them.  

You need to go through some vaguely numbered folders and open vaguely numbered files with notepad or notepad ++ within those folders to see the controller profiles.

I'm actually making progress editing and saving the defaults, so fingers crossed.  Trying to save a "null" profile that you've cleaned out completely equal CTD.   Just an FYI.

No, I'm not doing this, we pay them to check that the software works, or at least that patches don't make it worse, they have to change how they work or fire someone, I can't believe how bad they're doing.

For what its worth, I have not had CTD's with the update today, but contrary to what is posted earlier in this thread, My controller profiles are custom, not the default.  I use the T.16000 joystick with the corresponding Throttle and Rudder pedals, all have custom controller profiles that I created, and when I started the sim this afternoon after the update, I was able to change my sensitivity settings for the rudder pedals and save them to my custom profile.  No CTD at any point with today's update.   I do not use FSUIPC yet.

3 hours ago, wthomas33065 said:

Totally agree, especially now that I find out I can't modify the settings even if I get back to default.  So I'm stuck using my default profile which I don't like until the fix it.....  Very frustrating.  I had hoped it was something about "old profile" vs "new profile" but apparently you can't save a new profile either......grr.

I backed up my current wgs folder which apparently contains my current controller profiles with the hope that once Asobo comes out with a fix I can restore the wgs folder and recover the profiles. Whether this is a good idea or not I have no idea. Maybe the fix will work with the 'existing' wgs folder. Sigh.

Thanks for your work on this issue,

Al

Edited October 30, 20205 yr by ark

So the fix DOES work, it's just that you can't save a "null" profile.  That is a profile that has no assignments to it.  As long as a profile has at least one assignment, it can be properly saved.  

I save (Null) profiles with only one button assigned for my Yoke and Joystick so that their axis don't conflict by being active simultaneously.   The Yoke can be a little fluttery

I have finally restored both my CH Products Yoke and My Thrustmaster HOTAS X.  I really think it was with the old profiles.  Now that the settings are saved with the new profiles, they seem to be working.  

Pretty inexcusable, but at least I'm working now.  

It was an excuse to buy pizza tonight.   I hope it helped some of you.

I may buy FSUIPC or at least try the beta to avoid doing this all over again.....(Now if only FSUIPC 7 beta had a manual so I could learn how to use that....jeez 😖)

Edited October 30, 20205 yr by wthomas33065

5 hours ago, odourboy said:

Does anyone know where the profiles are stored? I'd like to grab them before I start my sim.

C:\Steam\userdata\94959374\1250410\remote

(this for Steam installation). (find the userdata folders for non steam installations.

I have just proved that the culprit IS 'profiles'. Applied the fix as per wthomas's instructions. Sim started without a murmur. Flew it around some, but noticed that the controls (joystick) was very jerky. So I went and created a new profile for just the stick getting rid of ALL the buttons and axis. FSUIPC7 controls the lot. Carried on flying with nice smooth controls.

Now the acid test:

Shut down and restarted the sim. Bet you can't guess what happened next. Oh, you did? 😄

 

6 minutes ago, Ron Attwood said:

I have just proved that the culprit IS 'profiles'. Applied the fix as per wthomas's instructions. Sim started without a murmur. Flew it around some, but noticed that the controls (joystick) was very jerky. So I went and created a new profile for just the stick getting rid of ALL the buttons and axis. FSUIPC7 controls the lot. Carried on flying with nice smooth controls.

Now the acid test:

Shut down and restarted the sim. Bet you can't guess what happened next. Oh, you did? 😄

 

I found out the hard way that a null profile does cause a CTD.  So instead, do what you did, but go ahead and apply ONE button to the MSFS profile.  Doesn't matter which one, but let MSFS have at least one button.  Then save it.  

That should work.

I routinely used "null" profiles to swap between controllers pre patch.  I use my yoke for the smaller aircraft and my stick for the larger ones.  I used null profiles to "disable" the non used controller because my yoke could be rather noisy on one of the axis and conflict when I was using the stick.

I think the presence of the "totally" null profile is what killed it.  I have seen others with similar hardware to mine who never had an issue.  Even now, if you create a "fully" null profile and save it, it will fail.

When I rebuilt my two new "null" profiles, I made sure to assign one button do them and now everything is working properly.  🤞

I'm in a quandary, now do I

A: Go through the recreation of profiles for everything with just one button assigned. Only for a patch to come out five minutes later so that I'll have to do it all again?

Or B: Shoot myself.

2 minutes ago, Ron Attwood said:

I'm in a quandary, now do I

A: Go through the recreation of profiles for everything with just one button assigned. Only for a patch to come out five minutes later so that I'll have to do it all again?

Or B: Shoot myself.

Well don't do 'B' Ron or we will have no entertainment left! 😄

Im going with this option:

4 minutes ago, bobcat999 said:

Well don't do 'B' Ron or we will have no entertainment left! 😄

Have a word with my missus. She doesn't think I'm the least bit entertaining. 🙁

Ron-

My Trolly Dolly has been advocating Thorazine for years now.... I like @odourboy's option!

Beck to P3D until there’s an official fix.

C

Edited October 30, 20205 yr by cavaricooper

1 minute ago, cavaricooper said:

I like @odourboy's option!

Me too.

13 hours ago, ShawnG said:

For what its worth, I have not had CTD's with the update today, but contrary to what is posted earlier in this thread, My controller profiles are custom, not the default.  I use the T.16000 joystick with the corresponding Throttle and Rudder pedals, all have custom controller profiles that I created, and when I started the sim this afternoon after the update, I was able to change my sensitivity settings for the rudder pedals and save them to my custom profile.  No CTD at any point with today's update.   I do not use FSUIPC yet.

That's because only certain USB devices cause the CTD. 

Steam user fix rig. From Asobo. Not my work.:

Good news for Steam users!
As you can see in my guide i was confused that MSFS switching “Steam Cloud” again after game start.
Here is solution.

• Open Steam client
• Navigate to Steam menu item
• Select “Settings”
• Go to “Cloud” tab
• UNCHECK the first option (“Enable Steam Cloud synchronization…”)
• Check that all files “inputprofile_XXXXXX” in “userdata\YourSteamID\1250410\remote” are deleted
  Now all your controller settings will store only on local machine.

And if you’ll open a controller settings you’ll that is your joysticks assignments are empty except gamepad.
Yes, only gamepad have own profile and it’s working well. DON’T CHANGE ANYTHING.
Again: DON’T CHANGE ANYTHING IN MSFS!
Sorry Microsoft Store users, i don’t have this version now and can’t check what to do if you bought your game here.
And also, your joysticks will work even if no profile, they will use default profile and you UNABLE to save your own. You can try to create it but you can select it.
Well done Asobo! Well done!

And UPD:
Once you start your simulator go to controller settings and you’ll see that is no profile name under controller name.

Click on “Preset Manager” and select duplicate. When game show dialog to save new profile click “Cancel” and now click on controller name and “Default” text will appear. Repeat it for ALL devices including mouse and keyboard.
Now you can see all your assignments but unfortunately you can’t save custom profile or edit “Default”