Goran_M

The right side of the H pattern requires a mouse or key/button command. Moving it across to the left requires a mouse. The left side can be controlled by your hardware axis like any other throttle. To get into beta/ground idle, you will need to assign a key command to "toggle thrust reverse", then it's controlled by your hardware axis. X-Aviation is the store that publishes the TBM. I (Leading Edge Simulations) provided the mesh, textures, lighting and animations. Systems and flight model were done by Saso Kiselkov (Hot Start).

Just a shot in the dark, but were you on the TCAS screen?

This is the section of your log that concerns me. It's something that is either not liking the TBM or the TBM not liking something else. However, in the backtrace, it's not the TBM crashing X-Plane. It's X-Plane crashing because of something else, as shown by the last 3 lines. If it was the TBM, it would be included in the backtrace. Would it be at all possible for you to remove all 3rd party plugins out of your resources folder, and then trying again? Then we can do a process of elimination to find the offending plugin. If possible, try replacing xPilot, because that was the plugin that is shown in the backtrace just before the crash.

To play it safe, if it's only on 1 PC, always deactivate the oldest one.

I can see a few things that might be causing this, but for now, can you remove or disable the "drgluck terrain radar" and try again. The TBM has it's own terrain radar, and it might be conflicting with the one you have installed separately.

https://discord.gg/xaQQPB

Some Windows updates change the OS to the point the add on recognizes it as a new PC. So you will have to go through the activation again. Remember, you are allowed 3 activations (not 5), and you must be careful not to FREEZE your current PC via the activation. Please watch the video for an explanation and instructions on activating.

Update your GPU drivers. The 3xx.xx drivers are very outdated and are likely the cause of the crashing.

Have you tried experimenting with your resolution. You may be getting the windows, but they are appearing off-screen somewhere.

The sidebar should be accessible whenever the aircraft is stationary. When you start moving, that is when the sidebar disappears.

Please read through this thread. When we know exactly what we can do, if anything, it'll be implemented. Until then, this is a workaround.

Do you have any kind of AI running?

Correct. The DC-3 will likely work in X-Plane 11's current state, but it may have unpredictable results. An update is being worked on to bring it up to full X-Plane 11 compatibility.

This is not something we can control or fix on the "aircraft" side. This is something the scenery developers need to look into.

There's nothing you can do on your end. You could ask the ground traffic author to implement some kind of debug info so he can see what's going on when the crash happens. Another example is that I've seen the JAR Design ground traffic cause the sim to crash many times, even with default aircraft. Adding debug info is very easy to implement for any dev, so it shouldn't be an issue.

Not at all. It doesn't upset me. But too many people think that because 1 payware add on works without problems, they all must work without problems. I just wanted to clear up that this is not the case. Check your scenery at your airport. Many times the scenery can cause the aircraft to "drop" onto the apron or the runway if it isn't created correctly.

First of all, the parking brakes. They work like on the real aircraft. You need to pressurize the brakes first. Apply brakes normally with pedals or a key stroke. Please note. When I say apply brakes, I do not mean apply parking brakes. Apply BRAKES, then apply parking brakes. The parking brakes hold the brake pressure. I'll address one thing you said in your post at x-plane.org. We ask everyone to please not compare payware aircraft with other payware aircraft. All payware is created differently, and therefore operates differently when other plugins are thrown into the mix. As for your other issues. Make sure you do not have failures enabled in the X-Plane menu. Before loading it again at the airport of your choice, try loading it at a default airport with minimal scenery. A good airport we use for testing is SCIP. Give that a try and post back results. Also, if it crashes again, please post your log.txt. Not your TBM900_log.txt

As I was reading your post, as soon as I saw "custom scenery/crashes started", I immediately thought of ground traffic. A few aircraft add ons have had problems with ground traffic, and it could be because of many different combinations of add ons or plugins. It's very hit and miss.

Could you include log.txt and TBM900_log.txt so I can have a look at what happened.

Thanks for this mini review. We're definitely looking at adding a few things. There'll be a couple of nice little surprises in the next update. Also, librain will be added in the future as well.

Are you talking about the stability of the aircraft or the engines?

Glass_Int_NML.png

We'll discuss internally and possibly reduce the reflection. In the meantime, you can open the normal map in photoshop and reduce the opacity in 5% increments until you're happy. Just back up the original

We know the issue, and we're looking at a way to fix it. It's not overly complicated, but it's something that could place the fault evenly on Laminar and us.

Many apologies, I didn't even see these posts. I'll bring these up with Saso and post back