Goran_M

Are you trying to introduce fuel too early? The NG given for an engine start is a minimum of 15%. Feel free to introduce fuel at up to 20% NG. Bringing fuel in too early, if the conditions are right, can lead to an engine fire.

I'll load up a flight and try to duplicate, then I'll post back.

Do you have any ortho scenery? If so, is it spread across 2 partitions?

150 is still too high for the ITT. You need to be at <120

Didn't even see this post. Apologies. I suspected scenery was the cause of a lot of CTD's. Mainly because the G1000 terrain radar trying to read terrain from 2 different drives.

The pilots are gender neutral

I've forwarded a similar log to toto, and he'll be looking into it. When you have time, can you check if it happens at the same airport/scenery, or is it random. Just for now, can you retry at the same area and see if it crashes again?

Strange. I'll look into it

We didn't change anything with regards to scaling or the oxygen mask. I'm guessing this was done on Laminars side.

I'm seeing a common thing in both of your logs. You both have quite a lot of errors in your custom scenery folder. The TBM looks like it's trying to read the navaid data in particular areas, can't read it due to the errors, and then crashing with the resulting error. By all means, take a look for yourselves. To help you diagnose, can either or both of you tell me where the crash occurred, and I will try to duplicate.

If they are present, delete all files and folders associated with the TBM in the Aircraft/X-Aviation folder, and try again

You can confirm you have DEFINITELY gone back into your account and downloaded the NEW installer and run it? I know you've said you've downloaded it several times, but you need to make sure the installer filename has 1.1.4b in it. Also, make sure you extract it out of the zip file before running it.

Just a guess, but did you take off the static vent covers and pitot tube covers?

I had a look at your log file and found this. "WARNING: extension missing proc glSpecializeShader. This is a problem with your video driver." The ice is using shaders, and it's almost definite there is something wrong with your drivers or the GPU itself. This is something you need to investigate on your end, as no one else is having this problem. This is a new feature that toto added. Propeller vortices under the right atmospheric conditions.

I'll check into the synthetic vision. The latest X-Plane update has made changes to the autopilot again. We're looking more into what needs to be adjusted for another update.

To put it bluntly, it's impossible to determine why this happening without knowing exactly what your entire PC configuration is with regards to your sounds. The only thing I can think of is there is some kind of conflict with either another add on, plug in, or your PC's sound hardware.

I was looking at making a new version for XP11. If I have time, I'll seriously consider it.

I didn't mean to say "You're the problem". I meant to say That's THE problem you are having. Sorry for any misunderstanding.

That's your problem. Press it so it reads "PRESS" then close the button guard.

You must be missing something. Check absolutely everything. I watched a streamer have problems with pressure, but when he landed, he discovered a broken pressure vessel. Make sure you go through your checklist. Check every item of the maintenance manager. Does the cabin gradually decrease in pressure? Is the cabin pressure dump button on PRESS or DUMP? It's the button on the ECS panel covered by a guard.

If this happens as you're climbing, you very likely have a leak in the airframe. Check the maintenance manager for any damage.

4b was just some minor fixes. Nothing drastic.

I'll look into it

Just to clarify, you're saying the course needle was not turning? Because the course needle doesn't turn by itself. You need to set the course yourself, and then the deviation bar will move according to where you are. For the deviation bar to move towards the centre, you will need to be on an intercept heading.

This one is a mystery and definitely an isolated case. I've watched 2 streamers this afternoon and they have no problem. I've also tested this on my system the last time someone reported this, and still no problem. You are, literally, the 2nd person to have this problem. Can you try unplugging ALL hardware and test again. Make sure you unplug hardware. Not just disable it. They need to be physically removed from the PC. Could you also post a log.txt file. Failing all this, could you also try re-calibrating your hardware.