TBM 850

Found it. Axes and Oh's does it. I have all my controls assigned with that. As soon as I connect AAO to the sim, it greys out the GeneralAvionics circuit, and I have to reactivate it with the avionics master.

image.png

Without AAO, the circuit is off on startup and comes on with the radio master, as it should.
Now I have to find out why AAO does this. Might be in the script for the TBM I use for StreamDeck. Tricky bitch...

Thanks for your help :)

Hello, long time :) can we expect to correct this issue in next update ? Thanks!

Can we expect that next update will proper simulate using bleed high and decrease TRQ?

@Black-Square said in Air conditoning "allows the cabin to be cooled before the engine is running":

I've already fixed it, as well. The fuel pump will also respond accordingly now by not cycling on and off when there is no fuel supply.

Nice!

@Black-Square said in Air conditoning "allows the cabin to be cooled before the engine is running":

MSFS 2024 compatibility update

Man, MSFS really dumped a load of work on you guys (3rd-party devs in general I mean) with the 2024 compatibility problems with 2020 planes.
Before getting the TBM, the main plane I'd been flying for months is A2A's Comanche, and FS2024 messes with its ability to restore the saved cockpit state, so I figure it's probably done similar things to the TBM850.

The TBM 850 does not have the "novel" style of power lever used in the TBM 900 and later, so you should find it much easier. The power lever, prop lever, and condition lever are three separate axes. The power lever can be bound natively in the MSFS controls menu, which is what I believe most of my users do, including myself. If you have a more complicated hardware setup, you can always write scripts for any kind of behavior you're looking for. Let me know if you have any questions, and I am always happy to help.

I have this problem only when I load the aircraft on the runway. Always CTD.
When I load into a parking position, everything is fine.
I have the TDS-GNX and the PMS50. The aircraft reverts always to the TDS, even if I set the PMS50 in the tablet. So there is something strange going on, perhaps also related to the CTD.

I believe you still need to copy the TBM 930 from 2020.

After many repeated flights..

The 750 and the 530 did not display LPV. They displayed RNP (sorry - my bad)

Tried the same approach with the Duke. The 750 displayed RNP, same result - no GS indicator

Tried a different approach. This one displayed L/VNAV on both the Duke and the TBM

Approach worked a treat.

So if it says RNP in the approach, I know it's not going to work.

@Black-Square I didn't even know it had some wingflex! Hahah the more you know! I do admire that you work on everything now, nothing is left behind. Thank you for your dedicated work!

That is great news, thanks for working on it.
Keep up the good work, your aircraft are amazing!

Not OP, but that's fantastic, I had just assumed this wasn't an option with the 750 setup. Thanks!

I have TBM 850 and Duke stutters as well in MSFS2024. Very bothersome in VR. Thanks for working with Asobo to fix this.

@limbo696

Hi All,

I wanted to let you know that I have been true to my word and applied my knowledge from the Starship to the KAS 297B. I have a solution now that functions as described in the manual, but can also still be used with native hardware bindings and the old functionality, if so desired.

This means that you will be able to use the KAS 297B, as seen in SteveO's videos (as discussed in another thread on these forums), with altitude arming, vertical speed arming, vertical speed synchronizing, control-wheel steering, and pitch adjustment with an associated rocker switch. The only exception is that altitude capture will automatically arm when a climb or descent is initiated in the direction of the selected altitude. This is a core MSFS limitation, as altitude capture is set wholly on or off in the aircraft's configuration files. It's possible that I will come up with a creative solution to this too in time. I will include this change in the TBM 850, and my Baron Professional and Bonanza Professional, which will be officially announced soon.

Thank you again for your discussion here, as it helps me prioritize new features, and gives me the insight to design them in a way that will not disrupt current users with my updates. Without you guys, I can't count how many features would not exist that I have become very proud of in my aircraft!

Think I may have discovered the problem on my system. It seems the flight plans take far longer to appear on the GS530 compared to some other aircraft.

Unfortunately, there is only so much that I can do within the limitations of the simulator, and most "workaround" features that I produce for my aircraft are the result of an embarrassing amount of trail and error to thread a fine needle between one rock and another hard place. What you're seeing here when sitting on the ground observing an ILS from the centerline is the result of MSFS's lack of easily accessible variables for navigation aids without querying a database. It forces me to treat many navigation aids as the same type of antenna, or directionally agnostic, for instance. For another example, the VOR's treatment close to the ground is a result of not using a terrain database and computationally expensive ray-tracing algorithms, but instead comparing the altitude of the aircraft to the receiver and applying various curves based on antenna radiation patterns and attenuation constants to arrive at a believable solution that is also light on performance.

All that being said, the reason I am often so delighted to have this forum is that it allows me to add requested features and changes to a never-ending list of items to revisit during future development. Next time I am doing work near my signal degradation code (likely for the Baron and Bonanza Professional), I will see if I can come up with some more clever tricks to improve signal integrity while operating on the airfield's surface for you. As is so often the case, I may already have some ideas of what can be done after looking at the code again while writing this.