TBM 850

Thank you so much for letting me know! That's an important one for me to remember as I bring the tablet into my other aircraft, so that was very helpful to hear! I too have noticed that the GNS will sometimes go through the startup sequence when the aircraft is loaded on the runway, and sometimes not. I haven't approached that like a bug, since it doesn't seem to have any related impacts on the user experience, but I have also not noticed any particular logic to when it does it and when it does not. I hope everything is working well for you now! Thanks again for helping me find this one!

I have the same problem I have found no solution. I’ve created a ticket three days ago and still haven’t heard.

This also happens to me each time I spawn hot on the runway.

Two workarounds I’ve found.

Cycle the radio master switch off and on again.

Select a non-GNS 530 on the tablet, load that configuration, then reselect the GNS 530s on the tablet.

Right on @Camo. I'm just glad you got it sorted out.

Cheers

Looking at the code, the approach arming indicator works the same as it does in all my other aircraft. It will illuminate when approach mode has been selected in VLOC mode with no valid source of navigation, or when GPS mode is selected and the GPS is not providing approach guidance.

@jheidebrecht said in Questions about Engine Performance NG/ITT/Torque since update:

My question is how are you maintaining a similar airspeed with a reduction in RPM? Given the same power setting, a reduction from 2000 RPM to 1900 RPM yields a 10-15 knot reduction TAS for me.

I did some rough testing some months ago and didn't see any significant loss in airspeed from 2000 to 1900 RPM but I only did it at one altitude and I don't recall what it was. I just assumed it would be fairly consistent regardless.
I did some more testing today at various altitudes of 10k/20k/30k and found large variances in airspeed with RPM variations.
At 10k it looked like my airspeed was fairly consistent from 2000-1700RPM and in two separate tests I seemed to gain a knot or two with lower RPM until I went below 1700RPM.
At 20k I maintained airspeed down to 1900RPM, lost about 4 knots at 1800 and then lost about 20knots at 1700 RPM.
At 30k I lost almost 20 knots going down even to 1900RPM and at 1800RPM it appeared I would just continuously lose airspeed and I quit when it appeared the aircraft would eventually stall.

Most of my TBM flights are around 1-1.5 hours so I don't often go to higher altitudes except for water crossings so maybe that is why I didn't really notice what you have already found to be true. From what I saw today I will watch more closely and definitely not run any lower RPM than 2000 above FL200.

Concerning the annunciator test button: I started the sim to double check that I wasn't using legacy interaction mode. Decided to start the TBM to re-test. And now it's working as expected.
Very strange, cause I tested multiple times yesterday.
Anyway, that report can thus be ignored further.

As for the GPS thingy, it's not a blocking issue for me. Glad that it's on your radar.

Thanks for the reply and to great add-ons!

@TPielhau I agree but don't expect an update pretty soon. As you can see in the linked thread, it should have been in this one already. At least it is a solution. BTW could be also an issue with the MSFS statesave since it is not the most reliable.

Wow.... How do you all find the most insignificant things to complain about? Time to go outside and touch the ground. It will be good for you.

OK, that's what I thought. It just looks silly if there is always a difference of 1 degree.
Thank you for implementing the tablet in the TBM850.

@RealPax thank you! I didn’t see it updated on the store page yet.

I had this short after the installation with one of the Duke's. And to start with, I am not sure how this works or if it only was a one time glitch.
It did trigger the switches behind the tablet. Moving the tablet to a different spot did fix this issue during this one time event.
So maybe worth a try. Just move the tablet to a completly different location and see if it will work.
I did not made any post on this since it was only a one time event for me.

I'm glad you enjoy the small detail. I was only prompted to add that a couple weeks ago, so I was happy to do it.

What I was trying to say with that last sentence was that if an aircraft has a GTN 650, you will see it in the avionics selection menu. It won't be hidden as some tertiary option. If you don't see it there, then it's safe to assume the aircraft doesn't support it.

I figured it out. It was a Blender eccentricity that I've encountered before.

Should definitely be fixed though. @Black-Square

That may well be. However, it is worth noting that prior to this update, to my knowledge, the TBM did not produce this specific behaviour.
If the avionics were shutdown after transferring to GPU power (before there was a cart), the power would not be disconnected and gauges like the primary engine instruments would remain on.
Before I turned it off, with extreme prejudice, I recall that the annoying "end flight" dialog box would generally appear at engine shutdown/mixture cutoff. My father, who has not removed that dialog box, saw it appear tonight immediately upon setting the TBM's condition lever to cutoff. Unfortunately, he had already powered down his avionics a minute or two prior, so we could not test the GPU issue.

@Zwoop68 Thanks all works 👍🏻👍🏻 Thanks

Great update !
Never mind for the sounds, they’re just a would be nice to have. On the other hand, what you gave us is really useful.
So many thanks for the continuous improvement of this wonderful aircraft. You’re showing respect to your customers… kudos for that !