Goran_M

This might be something you need to address with the developers of ACARS. The TBM does use code to drive the brakes, and this might be causing something to be missed as far as ACARS is concerned.

Make sure you have AP Trims turned on. You won't be able to trim the aircraft without it. Make sure you don't have any external scripts or any hardware assignments falsely setting your trim.

Not at all. These Charges definitely did not come from us. Best check with your bank and ask for a “chargeback” if they are found to be fraudulent.

For future reference, Hitting SHIFT + SPACE together will take a screenshot of the sim window, and store it in the Output folder in your root X-Plane folder.

No other plane has it because no other developer has implemented the pilot getting hot. Looks like you have warnings disabled, but the red is because all doors are closed and it's getting hot. A sidenote, the temps are being accurately calculated according to outdoor temperatures and cabin ambient temperatures. To cool down, just open 1 or both doors, or turn on the AC (as long as you have power connected or the engine is running.)

Can't say for sure. But it appears to be.

It wasn't the TBM that crashed the sim. You have some faulty scenery. It didn't even do a clean crash. The whole sim just stopped. I've posted a screenshot of the log file with the offending scenery. As you can see, there are no references to the TBM.

From the log being incomplete, it basically telling me the sim itself isn't finishing loading. Your drivers are version 432.00, and current drivers are 441.87 By all means, if it crashes again mid flight, please post another log. But try to update your drivers first.

It's crashing the sim even before fully loading. I can see you have very outdated Graphics drivers. Update those and try again. Please post back results.

The official line is: The foundation of the G1000 has all of Laminars underlying code in it. All the radios, airways, map drawing, etc... is stock G1000. Saso, the person who coded all the systems, simply added more features to it and customized it to reflect, on the surface, a TBM900 G1000. So, if there is a problem with the fuel estimates, due to the fact we are using Laminars fuel code, you will need to file a report with them so they can address it. For the record, this has been addressed already in several other forum posts. So we haven't ignored this topic.

Need the log.txt file. Not the TBM900_Log.txt file

Exception handler crashes are caused by AI traffic. But if it's CTD'ing without AI traffic, will need your log.txt file immediately after the crash

The red button is at the bottom of the Audio Panel.

Before starting the sim, disconnect your warthog hardware completely and then restart the sim to see if the problem persists. If it keeps happening, please post your log.txt file. If it stops moving with hardware disconnected, the problem lies in some kind of button or lever assignment in your hardware. If the throttle moves forward when it's on the right side of the "h" pattern, you have something assigned to your mixture controls by default (We've seen this before).

Check all hardware assignments and any scripts you might have running that control the throttle or mixture.

Confirmed bug in the charts code. It'll be addressed in the next update. In the meantime, avoid using the keypad entry into the charts name. Please use the scroll knob to select either departure or destination airport (via the MENU option>Show Departure Airport) and similar should work.

That’s what I thought you were seeing. Please change your Windows UI scaling to 100%. Your password field is hidden due to the larger scaling.

Can you post a screenshot of what you are seeing?

Do you have any kind of failures set in the default X-Plane menu?

We'll take a look

Works fine on this end. Did you adjust your curves at all? This may have had an effect. Also, check control stiffening.

Yes please. De-activate the GTN and Skunkworks. Please post back the results.

Are you running the GTN with the TBM?

The crashes will happen with AI enabled. Either within X-Plane itself or 3rd party. Again, please disable it until we figure out a way around it.

I can't really see anything wrong in the log. Does it happen to the same chart or does it happen to random charts? Can you try again at the same airport? Am I correct in assuming you can't get out of that page or screen after the freeze, and you also cannot select anything else?