Goran_M

Definitely revert back to non beta. Beta's are a work in progress, and it'd be like chasing a moving target if we fix something, and then they come out with another build that breaks it again.

As Rob said, we need the whole log.

We don't really use anything special with regards to ATC software like PilotEdge or Vatsim. The TBM will work fine on those. I'm guessing it's something to do with some kind of configuration with xPilot. Just as a precaution, make sure your MIC is set to "MICRO" and not MASK. MASK is used when you have your oxygen mask on.

Please see this post http://forums.x-pilot.com/forums/topic/15201-no-sound/?do=findComment&comment=134853

That's not possible, as the files we have are not tied to the DRM. The sound file sizes are correct. They are very small sound files, as you can see in my version in the image below. Something I just noticed by looking back at your log, I saw your nvidia drivers were seriously outdated, which is why I suggested you update your nvidia drivers, but after going through it a little more thoroughly this time, I found that the log file you posted was from a sim session where you had the Toliss Airbus loaded. I'll need you to load the TBM, let it finish loading, and then shut the sim down, and then immediately copy that log file out and post it here, so I can see what is going on.

Please update your GPU drivers. Nvidia drivers actually contain HD sound drivers. I'm guessing this will fix your problem. If the problem persists, please post back.

Can you post a log.txt file, please

The scenery errors can be ignored. As long as it doesn't crash, you're fine.

We need a full log.txt file. Also, may I suggest also contacting the developers of the other plugins you are using and sending them the same information. These lines are too vague for us to find out exactly what is causing the problem, as they don't state the nature of the problem 2019-10-12 20:30:05 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 2019-10-12 20:30:06 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 2019-10-12 20:30:07 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 2019-10-12 20:30:08 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 2019-10-12 20:30:09 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 and whereas I understand this problem doesn't occur with other add ons, the TBM is extremely complex, and is designed to run without crashing X-Plane in its default state, and no plugins installed. Introducing 3rd party plugins can cause starnge results with any 3rd party aircraft. If the developers of the other plugins can come back to you with some information for us on what to fix in the TBM, then we will definitely do so. For now, all we know is that any 3rd party traffic plugin, unless configured correctly (you can still run livetraffic, but after making an adjustment) will cause this crash.

This is definitely an audio issue, but it seems as though you are missing specific files in the TBM. Have you tried reinstalling?

Make sure you have the latest version. 8 months is quite a while, and I think we pumped out 1 or 2 updates since then. One of which was the FAA address for charts has been changed. Also make sure you're looking for charts in the US. Charts outside of the US won't be displayed. The exception is Europe, but you must have an aerorouters account. The X-Plane navdata should work with the G1000.

We can't help but to blame other software. The TBM runs flawlessly on most peoples setups. There are a handful of people who are experiencing this particular problem, and it is down to a conflict between the TBM and a slightly buggy plugin. Other aircraft don't have this issue because other aircraft either don't use a TCAS or use a very basic version of one. The TCAS in the TBM is very complex. In your case, even without a log file, I'm going to ask, are you running LiveTraffic or any other kind of traffic plugin? If the answer is yes, then the problem is easily diagnosed, and a fix is easily implemented on the users end.

As long as you have a ticket number, you will be seen to. It looks like a complex situation, but hold tight.

From what is known, it appears to be a bug with LiveTraffic. All the TBM is doing is reading the TCAS data and displaying it on screen.

These are the lights we used. https://developer.x-plane.com/2013/04/customizing-spill-lights-two-ways/

Please read this thread.

I'll bring it up with Saso and see if there's some way we can take care of it.

The gear was done this way because a single wheel wouldnt give enough "grip" for this aircraft. Please don't mess with it in Planemaker. Much of the landing gear is code driven, and making any changes may have unpredictable results.

https://discord.gg/tyrQUA

Nothing like this is planned. I'm not really aware of other add ons that offer this, though. You could always just open the map, and drag the aircraft on the map to the point where you want to go.

Going into the red for short times is perfectly fine. You just can't stay there for the duration of a flight.

We don't support beta builds of X-Plane. Too much can go wrong. Best thing to do, if you want to help Laminar get rid of any bugs, is to send them your log.txt file with a description of what happened.

There's nothing special about the landing lights. They are stock spill lights. This would be more a question for Laminar to answer.

https://discord.gg/g64RGu

I spoke to a Real Sim Gear representative, and he mentioned you already reached out to their support channels. We've forwarded this issue to Saso, and hopefully he may have some kind of a solution.