RobW05

I just asked because that was what happened to me once, tried to reset the generator dozen times but didn't realize the switch was accidentally in GPU position. Have you checked the maintenance menu, maybe you have a generator failure.

But you did set the switch back to battery? Otherwise you could reset it as often as you want, it wouldn't work.

The Navigraph FlightSim Community Survey published in December 18 had 11% VR users. It's growing but still a minority.

No, unfortunately it isn't possible. Unlike for buttons, Spadnext has no condition for axis.

I would really like to use Spadnext for that purpose, but it wouldn't work because we just have the two commands, up and down. We would need a dedicated command for cutoff, low idle, high idle and flight idle. Then it would be easily manageable to use a custom axis to send these commands at a certain point.

You are in revisionary display mode. Press the red button on the bottom of the left intercom panel to get back to normal display mode. That will resolve all your other issues too.

You've already asked in this thread, but didn't report back. Have you tried the suggestions, especially removing Lua scripts and checking double assignments for brake commands?

You´re welcome! Here´s the rudder response curve I use for the TBM900.

Just like DwightP980 said, I had a hard time too until i figured out not to follow the book and set rudder trim way right. A slight right rudder trim works best for me. Although it is of course depending on your hardware, I always set sensitivity and stability augmentation to zero and I have set a rudder response curve a little flatter than default in the first quarter. That gives me the fine control needed to stay on the center line easily. For landing I think speed is the key, if you're coming in too fast you will more likely have a hard time to stay on the centerline. Also don't forget to center your trims before landing, and never just slam in full reverse. Just take back power into beta mode right after touchdown. When you get your speeds right on final you will notice you need little to no reverse at all to get down to taxi speeds.

Yes, it's working again with 1.1.4c.

Are you running any scripts which might interfere with your brakes? Try removing flywithlua and check brake command assignments for joystick and keyboard. Sometimes accidentally double assignments are causing problems. Regarding your crashes: It's worth trying to remove all plugins and see if you still get crashes. If not, move them back one by one and see which one causes the crash.

Electric elevator and rudder trim is on the left side of they yoke.

I will do that. xEnviro is at the top of my list of suspects, I have it installed but most of the time it's parked out of the plugins folder. Last week i thought i gave it another go, so that could have been it. On the other hand, in my today's 3 hour flight it was active without problems.

After more than 2 months of a rock solid TBM experience (no crash, no fps loss) with xplane 11.26 and 11.30, I have updated to 11.31 yesterday and same time updated the TBM to 1.1.4c. Sadly, on my first flight yesterday i had the "exception handler" crash after 10 minutes and still sitting on the ground preparing for my flight. I was just looking on some charts on a external tablet, so I'm sure the crash was not caused by something I was doing in the simulator. I have neither scenery spread across 2 hard drives nor have I enabled AI planes. So there's surely more contributing to that error under the hood. Today I have just finished a 3 hour flight without problems. I have no clue what the root cause could be on my system. Nevertheless, thanks to Goran and team for not giving up on this!

Oh sorry didn't notice that. In my sim these earphones indeed make a big difference.

Yes, wind is definitely pretty noticeable. People say this is the same in the real plane, I don't know as I have never been in one. But I can imagine it must be pretty loud as you are cruising around 300 knots. My tip: Grab the headset from your copilots seat, it's there for a reason.

Thank you very much for your hard work and especially for keeping us informed! This is a level of support I miss with many developers, but you are doing great with all aspects of support.

Impressive! Wish I had your knowledge of how to do stuff like that!

Hello gorrack, this is a known issue with the particle effects introduced in 11.30. As a workaround the developer has included an option to turn off the heat blur in the TBM plugin menu. It will have to be adjusted in the long run.

It's pretty easy, you are notified by email that there's a new version and you simply download a new installer from the store and just execute it.

Unfortunately there is no way to go back once a version is made 'final' by Laminar.

Just a thought: Could it be that the VHF signal is unreliable when received on the ground? I remember having read the devs have implemented a lot of custom code for the NAV radios. That would explain the different results on the ground and in the air.

Have a look at the recent threads.

Yes, you would most likely run into the same problem with the G1000. Hold off a few days, the devs will have a fix out shortly.

Never heard of that...