It’s not a general rule. I had a custom controller profile and do not have the CTD issues.
But you seem to have reproduced it and it matches other’s observations so something with the profiles isn’t right.
Is there a way to access them and un-assign the axis? Are they stored in files?
found that if i unplugged all my controls it would load, as i plugged them in one at a time found my thrustmaster TPR pedals was the culprit, getting message “this plugin is already running” as soon as i clicked to close this message ‘BOOM’ off it goes to who knows where ?
Hi guys, I updated my game I few minutes ago and had the same problem. After reading some of the latest posts I made a test. Without my Logitec X52 connected MSFS launch with no problem, but when I plug the joystick, a few moment after the game CDT. When in desktop, with the joystick pluged and if i try to load the game, the game CDT.
Saitek X52PRO + The 3 Logitech G modules + Track IR, and seem no problem for me.
Have to say i’m using Spad.next as drivers for the X52 and Logitech G.
I remember at one time on a previous version, they were “hidden” in some vague.xml files that had some weird names and you had to open each on up in notepad to figure which one was which, but now I can’t find them anymore. Previous patches may have altered that. If anyone with MS store version knows where to look, that would be grand.
I did a full search of my PC looking for *.xml and couldn’t find anything that I even recognize.
Actually i never had a ctd before with msfs. But now it crashed 4 times in 1 hour.
Logitech panels stopped working but was reinstalled. and is working again. But perhaps there is some conflict there ?. I realize they can not test all pc configurations but this was probably a bit hurried.
Yes, I am having the same exact problem.
Start game with any peripheral but Keyboard/Mouse? CTD on load
Start game with nothing but Keyboard/Mouse? Launches fine until you add another peripheral and then it crashes.
Guys, this is pathetic. Anyone involved in QA’ing and approving this patch should feel bad about themselves. This is a 100% reproduceable crash. You guys have had ample opportunity to release a good patch and continue to just screw it up every time.
I’m not saying this as someone ignorant of the whole software dev/QA process. I literally do it for a living. I approved a release just this afternoon on one of my products and magic it didn’t break anything because I QA’d my stuff and rejected the release until it was all fixed.
ButtOwipoLIVE I have a Logitech Extreme 3d Pro and the sim works fine.
Same CTD. Been flawlessly since 18 Aug 
Unplugged all my controllers, and I managed to get into the SIM!!
Will be troubleshooting
Same issue here… 3/4 of the way on the progress bar CTD.
Same here. Before the patch, not too many CTD.
Now they are steady. After 4-5 tries, I might get the sim to start.
I try to stay positive about this sim, but again, here is another major snafu.
This is getting quite ridiculous.
Same, Japan update screen before main menu crash…
230 replies - 54 votes. So most oft them don’t have any problem
For anyone that wants a fix, go to your install folder (if you got it from the MS store. Sorry if you didn’t no idea)
You’re looking for a folder somewhere like: C:\Users\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\
Go in there, open each file denoted with type of “File” in something like Notepad+ or Sublime text.
If it’s for a peripheral that’s not a keyboard/mouse, back it up somewhere else and delete the sub-folder it was in (if you get one that’s a bunch of blocks of numbers, leave that).
This seems to have fixed it for me. You get to rebind your peripherals buttons, but it at least doesn’t seem to CTD anymore.
EDIT: Opus explains it better here: CTD after latest update (Update #5) - #242 by Opus7773889
Yeah peripheral issue, remove all but keyboard mouse works.
Has anyone checked what update version of Windows that they are using? I’ve yet to install the latest Win10 updates and I don’t seem to have any issues so far.
From what I’ve read, it seems to be a driver issue somewhere in the program stack. If I remember correctly, the latest Win10 update done something about security checking drivers, requiring them to have signed certificates?? Could be a new conflict if people have the latest Win10 updates??
This one seems to rest solely on Asobo. See my post up-thread a bit. Deleting the previously created peripherals seems to resolve it. The crash comes when the “New device detected” window pops up in MSFS.
At a hunch, certain peripheral profiles from a previous MSFS version aren’t compatible with the new update (gamepads for example) and so MSFS detects them as a new peripheral, and that popup or something in the process related to it causes the MSFS process to die a horrible death when it sees other profiles or something.
IDK how their stuff works (or doesn’t) but there’s a fix up there if you check it.
I did the WGS search (after recalling this issue from the Alpha days), and found my two main peripheral files (both of which were okay). There was also an “extra” one for a peripheral that I never use (it’s a wierd 3Dconnexion KMJ Emulator Profile)- this one I deleted it and the directory that it was contained in. AND I AM BACK IN ACTION- so check your WGS directory folks!
Peripherals crash issue, on mine confirmed…silly regression in bugs.