Goran_M

Known issue that was discovered about a week ago. From memory, it only happens when the crash bar is up, but the battery is off. Will be fixed in the next update.

Please check all your calibrations and assignments. If this does not work, try a reinstall. I just tested, and it's working fine.

You'll need to make an exception to the Gizmo folder in X-Plane as well.

I see a potential problem. 16GB RAM, and you have a LOT of plugins installed. Plugins chew up a lot of RAM. Removing LiveTraffic just lightened the load on the RAM and that's why you didn't get a crash until much later in the flight, likely when you may have been approaching some dense scenery. Do you have a lot of orthoscenery installed? Are your settings dialled up very high? As a test, remove half your plugins, preferably ones that you don't use very often, and then try again. Just make sure you leave Gizmo in there.

Do you have any kind of script running that can apply the park brake without you knowing.?

Could you post your entire log after the crash? My guess is your settings are too high for either your RAM or VRAM. The TBM is very graphics heavy, with over 2 million polygons and around 40 different objects and textures. But it still runs on many systems as long as the settings are configured for the type of hardware you have.

The cockpit is closed and warming up. If you flew the TBM in a previous flight and left the battery switch on, you will definitely have a flat battery now. Go to the maintenance manager and either recharge the battery or replace it.

That's not so easily done. We're looking at the problem, and a fix is in the works, but we can't just contact another developer and tell them what the problem is if we're not experiencing the same thing. This is why we ask the people having problems to also send a log to the other developers to see if it's something on their end. Saso is certain it's the GPU or something the GPU is doing with the add ons you're mentioning. The combination of add ons and the low fps is a result of the GPU architecture going a little crazy when they're all running simultaneously. Even though it doesn't happen to other add ons in your case, it's not always the aircrafts fault. Wait for the update to get sent out to testers (there are quite a few fixes included), and we'll take it from there.

This might be a case where you need to delete the files in the state folder and reload the TBM. X-Plane 11/Output/TBM900/state

I'm at a bit of a loss on this one. I've run every kind of test I could on my machine, and cannot duplicate this behaviour. Luis, try what Ch. Cole suggested and post back. The only other thing I can think of as a solution is to delete the contents of your preferences folder, and re-assign everything, but that's a last resort.

Aready that long? Yes, after a period of a few "maybe's", it is still being worked on. I'll have a lot more to say about it, if nothing goes wrong with the schedule, some time next month.

Make sure doors are closed AND locked. Make sure cabin pressure is good. No leaks. Check circuit breakers for cabin heating.

You have a bunch of LUA scripts running with the Carenado Centurion. Can you send me a log file with just the sim and the TBM installed, and the TBM loaded?

Are you using xEnviro?

It's not FlyWithLUA. Can you please check into this and make the appropriate fix, then test again to see if the exception error happens again. If it does, please post another log file.

Could you please post a log.txt file after running the TBM? I'm suspecting something might be wrong with your hardware, but I need to make sure.

The TBM will not overwrite anything from other add ons or the sim itself. It does run outside the sim in some cases (engine parameters, ground handling, etc...), but it won't affect what the sim does to other add ons. Once you load another aircraft, the TBM, and it's code, is no longer running. When you say you lose abaility to set mixture, do you mean you have to "recalibrate" your hardware for the mixture? Are you running some kind of script (FlywithLUA)?

Interesting. Thanks for sharing. We'll look into it. And thanks for the compliments.

Did you check your maintenance manager for any damaged components?

Rob is our unofficial, self appointed, tech support guy.

Check your CG and make sure it isn't too tail heavy

"exploiting bugs in other plugins" isn't done deliberately by any developer. Also, I'm only echoing Saso's comments about how 1 add ons code can conflict with another one, in an exploitative way and cause a crash. These bugs are almost always accientally overlooked by the developer. An example is X-Plane crashing whenever the Saab was run with xEnviro. Jim (Saab coder)and Ben (Gizmo creator) combed through the Saab code AND Gizmo code to see if there was anything that could cause a crash. They found nothing. I approached Andrej, xEnviro's developer, and told him about this, and he thought I was crazy when I told him it's almost definitely something with his software. He finally relented and sent out test builds to a few testers, and within half an hour, the testers sent in results, and he found a bug within xEnviro that would cause it to crash...only while fetching weather, and only when the Saab was running. He was very surprised. Using that example, we could agree the Saab was exploiting an overlooked bug in the xEnviro code. It wasn't intentional by us, but it shed light on an annoying problem people were having, and it has now been addressed in the latest xEnviro update. Now imagine us approaching every developer, asking them to check through their code to see if there are any issues with their software. Wouldn't go down to well. In your case, I would bet money that it's a problem with IVAO. Unlikely that it's teamspeak. As I said, I'll note this down and present it to Saso. If it IS the TBM, you can bet he'll find it and fix it. In any case, we appreciate your patience.

These are not that easy to isolate, due to the fact in a lot of cases, it's the TBM exploiting bugs in other software. I'm not saying this is happening 100% of the time, but it does happen a lot. Check your log.txt file after a crash, and scroll down to the bottom. The "backtrace" should tell you exactly what caused the crash. In your particular instance, the crash could well be a combination of IVAO and Teamspeak, AND maybe another plug in or plug ins, along WITH the TBM. Of course, we'll take a look and see what can be done, but the difficulty of this depends on what other plugins you have, and if any of those have any bugs in them. First step is the backtrace.

When you run the Saab, does everything work as it is supposed to? You should have a section for commands relating to the Saab.

No. X-Plane doesn't keep a log of actions you perform in the aircraft.