Anyone having blurry textures now?  Can't even read my cockpit.

45 minutes ago, stubbornswiss said:

I read a text from FlyByWire stating that there were issues with the latest update affecting their mod.

Yup lost attitude Indicator, and seem to be locked on Air France skin despite trying to change, default aircraft AP worked fine first flight.

16 minutes ago, abrams_tank said:

Some people are reporting in the official MSFS forums that certain devices such as joysticks and other flight simulator peripherals connected when MSFS launches is causing CTDs.  You may want to unplug them and start MSFS to see if you can get past this screen.

I'll disconnect everything, but I do not see the point since I will need my usb peripherals.

Update: Sim loaded.

Edited October 29, 20205 yr by DJJose

8 minutes ago, markk70 said:

 

2 Saitek throtttle quadrants and a Thrustmaster T16000M Joystick.

 

11 minutes ago, espent said:

I have TM Warthog and Saitek Multipanel and trimwheel. What are you using?

 

 

13 minutes ago, markk70 said:

Yes this works for me too!

My Thrustmaster HOTAS X is causing the problem.  Also, now (don't think it's related) I'm having issues getting my CH Flight Sim Yoke detected.  Also CH Control Manager is locking up.

But it's definitely the Thrustmaster HOTAS X causing the CTD.  That's been verified.

Disconnected peripherals. Loaded OK.

Reconnected while running. CTD.

Now to figure out what settings need to be cleared...and where they are.

 

Edited October 29, 20205 yr by tailspin45

No problems at all after the update, i even try to get a nice score in the new Halloween challenge 😂

3 minutes ago, DJJose said:

I'll disconnect everything, but I do not see the point since I will need my usb peripherals.

It's a method of debugging in software development.  You want to make everything as simple as possible for the software so you can isolate the problem.  In the case of MSFS, this means removing stuff out of your Community folder so that it is empty, disconnecting peripherals, etc.  You want to run MSFS with no modifications and no peripherals attached (since MSFS will try to detect and interface with peripherals).  If that passes, then you add each modification back, one by one, to isolate the problem.

Edited October 29, 20205 yr by abrams_tank

24 minutes ago, espent said:

i just disconnected all USB ports except mouse and keyboard, and guess what?

it loaded!!

Same here! All usb devices disconnected and now the sim is starting (before CTD every sim start)!

Devices: Saitek Yoke, Honeycomb Alpha, Saitek FIP (x2), GoFlight MCP Pro, Playstation controller

Works. Tried a small flight in the 172.

The elevator authority fix is great. Thank goodness.

The sensitivity changes allow me to set up my CH Pedals so they work. Thanks goodness. Although my crosswind v2 will be here soon, so w/e.

Didn't notice FPS change but it does look nice.

That is all for now.

The other thread about the CTD showed some victims found that unplugging controllers and/or hubs allowed the sim to run. That's a clue concerning the problem. Maybe existing sensitivity settings are out of bounds with the new sensitivity controls?

 

 

Just now, tailspin45 said:

Disconnected peripherals. Loaded OK.

Now to figure out how to reinstall them.

 

I suspect it is related to the new controller sensitivity options. 
what if you delete your controller profiles? Does that work?

Hope you guys sort the issues out ASAP and get back in the left seat! Pretty bad that every time we do an update, we have to hold our breath and hope all goes well.

4 minutes ago, wthomas33065 said:

I'm having issues getting my CH Flight Sim Yoke detected.  Also CH Control Manager is locking up.

I have CH Products yoke, quad and pedals and no CTD, so it is a strange one for sure. BUT you should not be using CH Control Manager.

Edited October 29, 20205 yr by RaptyrOne

You geniuses! Removed USB peripherals and now it loads.

I’m only getting a ctd when I try to upload a flight plan from simbrief and then input the approach

Just now, DJJose said:

You geniuses! Removed USB peripherals and now it loads.

So the problem is, MSFS will try to interface with your peripherals on loading the game.  That's where the bug is.

Remember in the future, this is how you debug software 🙂