October 29, 20205 yr Just now, AmeliaCat said: try total reinstall I'm not redownloadng 90+ GB if I can help it. That's not realistic.
October 29, 20205 yr 42 minutes ago, raymar said: Heck, I have a ton of USBs. All of the Saitek/Logitech panels and FIPs. I'm off to screw up my setup to see if MFS will start. duh. I am not going to be so eager to add the updates from now on. Ray You have no choice. Patches are mandatory. MSFS
October 30, 20205 yr I'm getting the same problem ... SIGH .... Tried with my USB devices unplugged ... same problem. Adam.
October 30, 20205 yr I'm in the same leaky boat, but at least people have posted on the official MSFS forums that Asobo is aware of the CTD caused by certain controllers and is working on it. But that aside, I've never seen such a buggy update process.
October 30, 20205 yr Thomas has found a fix for this (if you only use FSUIPC to calibrate rudder axis). The CTD is caused by any controller that was previously calibrated for rudder axis, my case rudder pedals. When you unplug this peripheral the CTD no longer replicates. If you delete the folder (go to Thomas link) where the rudder axis was calibrated/set, you will no longer CTD. SN737
October 30, 20205 yr 14 minutes ago, SergioN said: Thomas has found a fix for this (if you only use FSUIPC to calibrate rudder axis). The CTD is caused by any controller that was previously calibrated for rudder axis, my case rudder pedals. When you unplug this peripheral the CTD no longer replicates. If you delete the folder (go to Thomas link) where the rudder axis was calibrated/set, you will no longer CTD. This is not a definitive fix however. There's plenty of people like me who unplugged all usb and still get the CTD. It's more than just controller profiles. Also worth mentioning that once people are reconfiguring their controllers, it goes back to crashing. And I think it's a little drastic to go deleting all our profiles. Give it a day and see if they come up with something. Seeing people blowing everything up and redownloading/reinstalling is just impatient. Is it that tough to go a night w/o MSFS? Edited October 30, 20205 yr by bahnzo
October 30, 20205 yr 2 minutes ago, bahnzo said: This is not a definitive fix however. There's plenty of people like me who unplugged all usb and still get the CTD. It's more than just controller profiles. Also worth mentioning that once people are reconfiguring their controllers, it goes back to crashing. And I think it's a little drastic to go deleting all our profiles. Give it a day and see if they come up with something. Seeing people blowing everything up and redownloading/reinstalling is just impatient. Is it that tough to go a night w/o MSFS? I should have specified that this is a fix if you use FSUIPC to configure all your axis and do not configure any within msfs. This fixed CTD in my case 100% SN737
October 30, 20205 yr I'm in this too now... ASOBO!!😡 R5 3600 - GTX 1070OC - 32GB 3200 - NVME - 3440x1440 160Hz - VR(Quest 2) GarbagePoster™
October 30, 20205 yr I had a similar issue after the first update. It turned out that my hard disk had gone bad and a couple of the files got corrupted. When I ran chkdsk it listed two flight sim files as bad. I deleted them and when I restarted the game, it automatically re-downloaded them and was ok. Since then I replaced the bad disk with an SSD.
October 30, 20205 yr Author 4 hours ago, DJJose said: You have no choice. Patches are mandatory. Not to switch back to another sim. When Pigs Fly . Ray Marshall .
October 30, 20205 yr Mine does not hangup at all (I uplugged all 5 of my flight controllers from USB) and it booted right up. Then shut MSFS down re-plugged controllers in, and it all works fine. Thanks for whomever posted the unplug tip, it worked for me. 5800X3D, RTX4070, 600 Watt, one or two 1440p 32" screens, 64 GB RAM, 4 TB PCle 3 NVMe, Warthog throttle, VKB NXT EVO stick, Honeycomb Alpha yoke, CH quad, 3 Logitech panels, 2 StreamDecks, Desktop Aviator Trim Panel. Crystal Light VR.
October 30, 20205 yr 5 hours ago, SergioN said: I should have specified that this is a fix if you use FSUIPC to configure all your axis and do not configure any within msfs. This fixed CTD in my case 100% I also have all my controllers mapped via FSUIPC7 ... but I still can't get past the CTD. I'm able to start up OK start up with no controllers, after which I can [successfully] plug in my X52 Pro, but as soon as I plug in the rudder pedals, I get the CTD.
October 30, 20205 yr Starnge. Fortunately for me its ok and I have many USB connected (more than 20....). Its good idea to check your BIOS and update for the new Edited October 30, 20205 yr by YoYo Webmaster of yoyosims.pl.Win 10 64, i9 9900k, RTX 3090 24Gb, RAM32Gb, SSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5 [MSFS, P3Dv5, DCS, RoF, Condor, IL-2 CoD/BoX] VR fly only: HP Reverb G2
October 30, 20205 yr 5 minutes ago, YoYo said: Starnge. Fortunately for me its ok and I have many USB connected (more than 20....). Its good idea to check your BIOS and update for the new Wait .. this is for controllers that have worked perfectly in P3D, XP11 and MSFS 2020 until right now? If I had a BIOS problem, I'd be having many problems before now. Anyway - updating Saitek/Logitech drivers is a total nightmare. I'm not going down that route just because Asobo stuffed up their latest "update".
Archived
This topic is now archived and is closed to further replies.