Goran_M

Anything to do with the airways or the navigation of the aircraft via the G1000 ultimately falls on Laminar, as it is their G1000 we're using as a foundation. Everything else that is TBM specific is custom coded. So your best bet would be to contact Laminar and let them know the issue with the airway.

1. Yes. Map a button to "Toggle thrust reverse". This will bring the power lever back to the beta mode and you can taxi. Bringing it back further will bring it into reverse. 2. If navdata is new, it can sometimes take a few weeks or a few months to make it into the next navdata file. However, in saying that, make sure your navdata is up to date. 3. You can literally download the actual TBM operations manual and use that. There are links in the documentation we have included. Here's one of them with the performance data included. https://www.tbm.aero/wp-content/uploads/2016/03/PIM__900_AN__E0R2.pdf

Make sure you enable the COM frequencies via the Audio panel (The panel to the left of the PFD). Not enabling it there, and trying to enable it in XPilot may very well be the cause of the crash. Also, check your display drivers. Possibly consider reinstalling them, because the log does show some kind of display driver issue.

This is the part that is sticking out at me. It's not the TBM crashing. It looks like something inside XPilot and something to do with your display drivers. Do you have some kind of extended monitor setup? The TBM can act unexpectedly when using a multi monitor setup that is not configured correctly.

Yes sir. I modelled and textured the TBM.

Oops. Sorry. I totally missed this one.

We're investigating further. I'll post back here with possible solutions.

Can you try the following: Remove all 3rd party plugins except Gizmo and remove your state folder (found in X-Plane 11/Output/TBM900) and try again. The state folder will rebuild itself.

Have you tried at different locations. Can you try at a default airport? Sometimes we see crashes like this when the scenery has corrupt terrain data. The reason you're not seeing it with other add ons is because the TBM uses a ground radar. If the crashes stop at a default airport or a different airport, the problem is almost definitely bad terrain data.

Due to the underlying Laminar G1000, this isn't possible without rewriting large chunks of the PROC entry page.

https://discord.gg/EBrPTk

The speed is obviously dependant on several factors. Cold air temps will increase engine efficiency over warm or hot air. Higher altitudes will increase take off run over lower altitudes. Not to mention weight and fuel. It could also be the pilot controlling the distance it takes to get the aircraft off the ground. Some pilots may choose to do a slower take off roll by not fireballing the throttle. I understand you are comparing YouTube videos of the take off roll, but you have to keep in mind this is a single engine GA aircraft made up of composite materials with a PT-6 engine jammed into it. Rest assured, we had one of the owners of Foreflight, who owns the aircraft we used as a reference, work very closely with us on the flight model, and he provided us with constant feedback on all areas of the flight envelope...down to the time it takes to stop the aircraft vs aircraft weight. Based on his input, we're confident we pretty much nailed it. As for the take off torque, we may look into it some time in the future.

https://discord.gg/JepDf8

Will need the log.txt file out of the root folder.

It's been a while, so I may be wrong. The lower disc is a directional Gyro. It cannot be adjusted. You are supposed to adjust the adjustable heading disc to the heading you want to fly towards, then turn the aircraft so the non adjustable DG lines up with the one you adjusted. Then enable heading autopilot. It'll hold that heading now.

https://discord.gg/nQfzUD

I just tested this myself. I am unable to reproduce it. I even pushed the crash bar up, pressed the buttons on the audio panel, and still nothing. My essential bus avionics turn on with the crash bar up, but no radio static. Do you have any kind of avionics hardware, scripts, external 3rd party ambient atmospheric add ons, etc... that could be causing this? Anything at all?? No matter how insignificant you might think it is.

The COM radio is on the essential bus. Meaning if the crash bar is up, it will provide power to the radios and the left PFD. Pull the crash bar down and the sound should stop.

It appears it's linked to the COM volume. Just turn it off on the audio panel. Can you confirm if the crash bar is up or down?

Had to edit my original post. Sorry if it caused any confusion. It was pretty late. Anyway, it could be something as simple as a rogue button assignment. Check all assignments and if you have any LUA scripts, check those too. Should be a fairly simple fix.

This could be something as insignificant as the openGL. There will always be CPU processes done in the background. Especially with other plugins running and scenery loading. If it's only minor and sporadic, with an occasional dip for a microsecond, just try to ignore it. When XP11.50 comes out, these drops should be all but gone.

It's unlikely the crackling sound is caused by the TBM. We haven't had anyone else make a mention of this, so that leads me to believe this is some kind of local issue or slightly corrupt install which was fixed with a reinstall.

Go into your settings and try to increase the number in your flight models per frame by 1 or 2 from it's current setting.

Please unplug all hardware and reload the sim. If the trim is not pegged to the left, the problem is with your hardware.

You can have an opinion. No one will roast you for it. But there are major changes coming in X-Plane. Austin has been dealing with people telling him he's crazy for over 20 years, for keeping a flight sim going for this long against Microsoft. That he can never hope to be successful. He continues to prove them wrong.