Goran_M

When you're running these kinds of tests, it's recommended to completely remove the plugin folders, then replace them 1 at a time. When you remove them, put them on your desktop or some other folder completely outside of X-Plane. Disabling them doesn't prevent them from loading when you start X-Plane.

That was my next suggestion. Try 3 or 4 flight models per frame

I'll experiment some more with the colors on the panel and the switches. Trying to find a good balance for the color between night and day can be a little tricky. I'll try and make it in time for the next update.

If the aircraft is going crazy on landing, make sure your yaw damper is OFF.

Ah, you want descriptions. I'm not entirely sure that can be implemented to the extent you would like. The manual should cover everything you need, though.

Well, that was fast!

Yes. And thank you. Please enjoy

For now, it's a well earned rest for both of us, and Cameron. We're still working on other fixes, but not at the pace of the last week. We've had discussions about future projects, and we work very well together, to the point that it was my pleasure to be involved in this project. Take from that what you will. But for now, speaking for myself, it's time to spend more time with my family and my daughter.

Of course.

I'd say that is definitely it, in your case.

Matt Davies once did a stream where the engine cut out. In his example, he caused the aircraft to climb sharply and then drop. When this happens, the fuel doesn't get fed through the fuel lines, and the engine will cut out, until fuel flow is restored and you restart the engine again. I'm guessing this might have happened in your case. Could you please confirm? We're all workaholics.

If you think this is a bug, can you please post a Log.txt file. Before you do, can you confirm you didn't over torque the engine?

You can disable them here. (Lower Right)

Toto has worked continuously, since release to fix as many issues as he can. We're working as fast as possible. 5 updates in less than a week, with this many fixes is not an easy task. We know you paid money for the product, but yours is a rare, almost isolated case, and it's very hard to pin it down to a cause. While you are waiting, have you tried removing all other plug ins, and then running the TBM. If you CAN run it, then it's another plug in causing the problem. Otherwise, we will investigate further.

Toto is looking into this. Hopefully, it'll be in the next update.

This is not recommended. So much is going on in the TBM, by way of custom code, that bringing in another nav device can have seriously unpredictable behaviour.

Turn off the Aux Fuel Pump.

You're pretty much spot on there. My specs: i7 6700K GTX980ti 32GB RAM

Difficult question to answer. But I do have 3 installs of X Plane on my PC. non-beta with plug ins. Non beta vanilla install and beta with plug ins. What I found was, if you can run a clean X Plane comfortably, you will have no problems running the TBM. There are some plug ins out there that can drag performance down significantly. That's why it's sometimes a good idea to remove them all, and put them back, 1 at a time, to see what plug in is causing the performance hit.

No. This add on has been designed to reflect, as close as possible, real world operations of a TBM 900. It is definitely not a LITE version.

Throttle quadrant.

Just a note on this. We chose SCIP purely for the short loading times. We depended on our testers and streamers to test it at other airports. Strangely enough, they were all getting good performance.

You should be getting SOME improvement in performance. The minimum performance improvement I’ve seen is 5fps.

The latest update has people gaining up to 14fps. And I have more optimisations planned over the next day or 2.

Navigraph will be in a future update.