Goran_M

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.

It really could've been one of a few things. The TBM we made will have failures depending on what you do to it. It could've been something as minor as moving the throttle lever slightly forward while the engine was off. You will really have to follow everything by the book on this aircraft, otherwise issues, small and large, will eventually come up. And nice to see another Goran in the X-Plane world.

To zoom in and out of the actual map, you can use the zoom knob on the FMC. There is no setting to enable or disable. The function is already implemented in the relevant manipulators.

We need the entire log file. Because that error is so vague, the first, among many things we look at, is what other plugins are installed.

It already does. Wherever you see a half circle arrow cursor, is where you can use the mouse wheel to rotate the knob CW or CCW.

Can you try removing your state folder files, then restart the sim with the TBM? (X-Plane 11/Output/TBM900/state) Do not delete them. Just move them somewhere temporary. When you reload the TBM, the files will be rebuilt. Test again and please post back.

Do you have any scripts running that could interfere with the TBM systems? Have you checked the maintenance manager for any issues?

No. They are not linked.

If the prop isn’t budging, it’s because you have no power going to the starter. Have you watched the included tutorial to make sure you haven’t missed a step?

log.txt is found in your root X-Plane folder When you install the 2nd TBM, just point the installer to the other X-Plane folder. Make sure the X-Plane folder is labelled differently or is on a different hard drive.

You can post a log and I'll take a look. If you install a fresh copy of X-Plane, it will not install OrbX. OrbX has it's own installer.

Ok, my suggestion is to first uninstall the TBM, then delete all TBM folders in your Aircraft/X-Aviation folder. But only delete the folders AFTER uninstalling. You should definitely not have 2 TBM folders, then reinstall a fresh TBM. Next, you are perfectly safe to install as many copies of X-Plane as you wish on the same PC. I have 3 on my machine. But keep this one as a testing installation of sorts, as long as you have the HDD space. As long as you don't install any other scenery or aircraft into it, you'll be fine. I'm not sure how other developers DRM works, but seeing as a bare X-Plane installation would only be used as a testing platform, it wouldn't matter. Of course, this is all up to you whether you want to go down this road, but keep in mind, it will help, not just us, but many other developers, in diagnosing potential problems, as many problems arise from plugin conflicts.

I'm honestly stumped. The only other thing I can think of, is to install the TBM into a bare installation of X-Plane, freshly installed, no plugins or scenery, and test. If it works in that one, then the problem is definitely in the original X-Plane install.

Do you have any scripts running that could be interfering with the start procedure? I just loaded the TBM 10 minutes ago, and engines started without issue. (11.34 btw. DO NOT use the beta. If you do use the beta, any beta of X-Plane, do so at your own risk and expect problems.)

@JackSwyr @French_Pilot Check your maintenance manager and make sure everything is "as new".

Watch this video of a streamer going from cold and dark to full flight to see where you're going wrong. https://www.twitch.tv/videos/443511582?filter=archives&sort=time

This kind of error only happens occasionally and under specific circumstances. The major problem with it, as it states "something has reinstalled our exception handler", it does not state what has reinstalled the exception handler. So it's almost impossible to pinpoint. It could be to do with the location, plugins that are running, or some other kind of random element. If it keeps happening repeatedly, I'm afraid the only other thing left to do is to remove all plugins (except Gizmo), and re-try, while adding the plugins back, 1 at a time, and trying each time until it happens again. That will tell you if it's a plugin related issue.