Goran_M

Excellent

Ok. Sorry I couldn't be of more help.

Would it be too much to ask to try installing another copy of X-Plane, on another partition or hard drive, with no add ons and no scenery. Just a bare X-Plane installation and then the TBM. You don't have to delete your original version of X-Plane or the TBM.

I've made Saso aware of this thread, and he'll be looking in on it soon. Just one more question. Does this happen at every airport? Have you tried loading the TBM somewhere in Europe? Can you try loading it at an airport with default scenery. Sometimes scenery can wreak havoc with 3rd party aircraft.

Remove (Do not delete) CEF, FlywithLUA, Little XpConnect, SAM, SimShaker, Skuncrafts, TolissData, WorldTraffic, X-Camera, Xchecklist, XPlane10Connector, XSBMsgSound. Leave everything else. Try again and post back.

Can you post a screenshot of the folders in your plugins directory before you removed any of them? ie. Replace all the folders and files, then take a screenshot and post it.

Ok, this is a very weird one. I've seen something like this happen on a Mac, but not on a Windows machine. I've let Saso know about this, but in the meantime, can you try deleting the Skunkcrafts updater plugin? I've seen this give us our fair share of issues for some reason. Failing that, you may have to move all plugins out of the plugins folder, leaving Gizmo in there, and then trying. THEN, if it works, we've at least narrowed it down to a plugin conflict.

Please remember, the G1000 included in the TBM is heavily customized, so it will work very closely to the real thing. There are only a few things have been excluded from this one due to Laminar's limitations of the default G1000, which we used as a foundation. I have just tested this myself in 11.36, and everything is working as per normal. Assuming the installation went without a hitch, I can safely say you are missing a step somewhere, either in the flight planning procedure or some other system. In either case, please post back on how you go.

Oh boy. You're really taking me back and testing my memory now. The old Sperry's are a unique autopilot. I'll have to go back and look into what I did.

I'll get you to try one more thing before I call in the big guns. Delete all the contents of your X-Plane 11/Output/TBM900/state folder. Then try again. Please post back results.

Before we get into what might be causing this, can I confirm you are turning the AP Trim switch ON (overhead panel) and then when wanting to engage the autopilot, you press the autopilot button on the AP panel. In case all that is being done, do you, by any chance, have any kind of scripts, or do you have some kind of Saitek hardware with assignments that could be overriding the autopilot? This is usually the problem with certain systems not working. Also, check that all X-Plane failures are set to off (ie. always working)

First try updating your nvidia drivers. They're a little outdated. If that doesn't work, please post back.

Nice catch. Will be fixed for the next update.

Beautiful. I'm in the midst of getting a similar type of flight organised (for myself). Keep posting.

You'll need to register on auerorouters to get European charts.

you'll get more of these little surprised. Just be prepared. All part of the wear and tear.

CPCS backup is a mode of the GASC (Global Air Supply Controller) when it loses certain critical sensor inputs (such as cabin pressure differential, or aircraft barometric altitude). Basically the controller then can't provide reasonable cabin altitude control, so it defaults to a "safe-in-all-conditions" cabin altitude of 9800 ft. Below 9800 ft your automatic outflow valve negative differential protection will make sure the cabin altitude doesn't exceed flight altitude by too much (meaning, the pressure in the cabin would be lower than the outside air). But above 9,800 ft flight altitude, the cabin will essentially become locked to 9,800 cabin altitude and stay there for the entire flight. For reference, this is in the POH in the ECS section.

Your best bet would be to go through support.

I have an idea what might be casusing this, but I'll send a DM to Saso and see if he comes up with anything.

One thing sticking out at me is your GPU drivers. They're pretty old. But the main issue I can see, and I've seen it before with crashes like yours. Please check the image and see what you can do to try and fix this on your end.

Can you post a screenshot of what it is you are seeing?

All I can say on that is we'll do what we can.

We'd rather publish 1 update fixing several issues than several updates fixing 1 issue at a time. Still a couple of things to fix.

The commands for the softkeys are: G1000 Softkey #1 through to sim/GPS/g1000n1_softkey12 They are the default X-Plane commands. Just tie your hardware to those and you should be good to go.

Excellent