TBM 850

I just looked at this on my end, and I see ~15% change in torque depending on inertial separator position at all altitudes.

Hi All, I have addressed some of these notes elsewhere, but I thought I would post them here too. Thank you for all the feedback. Autopilot UP / DOWN rocker switch I believe the current implementation is correct, but the KMC 321 Mode Controller's manual does not provide any insight into the directionality. Let me know if you can find something that documents this, and I will make the change. Autopilot BANK limiter This is a bug in the Working Title autopilot implementation. I thought I let a note in the manual, but I guess I forgot. I have mentioned it to them tangentially during development, but I will bring it up in earnest next time I write to them. If you are using the default autopilot implementation with the TDS GTNxi, non-WT mod PMS50 GTN, or no GPS at all, then the bank should be properly limited. Landing Lights I can never seem to make the exterior lights bright enough for my users, haha. I usually set the brightness to what I would expect looking out the windows of my own airplane, and then double it. No matter how much I increase the brightness, people always want more. Unfortunately, the light implementation in MSFS can produce comically bright halos around the lights during the daytime when the brightness is very high. Somewhere in between lies a compromise, which can always be override by mods. Windshield Anti-Ice on side windows The cockpit side windows have defroster vents, which can be used to deice the windows. The cabin windows have nothing. Unfortunately, the MSFS window deicing system is all or nothing, meaning that we cannot define parts that should be iced or deiced. I might see if I can come up with a clever trick at some point, but 90% of the features in my aircraft are "clever tricks" to get around the default MSFS limitations, and each one adds compounding complexity. V/S Autopilot I will still look into this. I just haven't yet. I'm not sure there is anything that can be done about it without compromising the autopilot's performance in turbulence, but I will see what I can do. Cruise speed at FL300 / 310 I cannot reproduce any performance disparities quite this dramatic, but what I have found is that low performance cruise (long range cruise) tends to be faster than book values, while high performance cruise is right on the book numbers to the knot. I chose to go with this approach, because I figured most simulator pilots would not be flying to save fuel, haha. I've made a tiny adjustment for the next update. Thanks for the feedback again! Nick C.

Hi All, I seem to recall hearing about this issue in my King Air, which is my other aircraft that uses dual 530's. I'm not sure why only some of the buttons would work, but I believe the problem with the default bindings is that when there is one 530, it is named "AS530", while when there are two, they are named "AS530_1", and "AS530_2". This means that ">H:AS530_CDI_Push", becomes ">H:AS530_1_CDI_Push" for the first unit, and ">H:AS530_2_CDI_Push" for the second unit. Whatever causes the problem, I know we sorted it out for the users in the past. If that does not work for you, please contact JF tech support, and they can use their knowledge database to find the solution that worked in the past. Hope that helps, Nick C.

@randolf Hey Randolf, I just wanted to thank you for saving me the trouble of positing this. That's exactly where that parameter lives, and how it should be modified. Happy flying!

@mad_x This is one of the last effects I have not included in the aircraft, since it's harder to implement than the ITT change. Given that I haven't gotten any complaints about how my custom fuel controller code is performing in the wild, I think I can add this now. I'll see about it for the next update. Thank you! Nick C.

Hi All, This is a bug in the Working Title autopilot implementation. I thought I let a note in the manual, but I guess I forgot. I have mentioned it to them tangentially during development, but I will bring it up in earnest next time I write to them. If you are using the default autopilot implementation with the TDS GTNxi, non-WT mod PMS50 GTN, or no GPS at all, then the bank should be properly limited. Thank you! Nick C.

Still can't see the runway when landing at night since 1.1

@andydigital I will look into that, thank you!

@fabristunt No, it is completely standalone

oh and another excerpt from an article I've previously posted about (https://www.flyingmag.com/pilot-reports-turboprops-tbm-850-even-faster/ ) This one discussed the qualities of the TBM airframe strength: Mach effects change with air density, becoming more critical as atmospheric density decreases with altitude. For that reason, nearly all turbprop airplanes adjust Vmo down as altitude increases, thus delivering a larger margin away from the detrimental effects of Mach as the airplane climbs. The creators of the TBM took a different tack and designed in enough airframe strength and flying qualities margin that the airplane exceeds all standards at 270 knots indicated airspeed at any altitude up to its 31,000-foot ceiling. The single red line Vmo of the TBM reflects both exceptional airframe strength, and very predictable and benign flying qualities at all altitudes. While some turboprops are limited by their Vmo at high altitude, the TBM never is. That is especially important on descent, where you can shove the nose over in the TBM on descent and gain back some of the time spent in climb by coming down at a very high true airspeed without a reduce red-line limitation.

For anyone interested, with the last updated version of SPAD, B vars are no longer supported, so the previous code will not work. I have done the same solution as @jim33152 proposed, using vjoy in spad.next can move the switch ---> after installing vjoy, run it, launch MSFS and in options go to Controls, there you will find your VJoy, then assign the native binding for the Propeller Deice to a joystick button in Vjoy. Finally in Spad, click on Add Event/button pressed/Advanced/Virtual Joystick and choose your Vjoy (probably it would be vJoy #1), for action choose "Press/release a button" and in "target" choose the same virtual joystick button that you chose in the general control options in MSFS for the Prop Deice switch. That is my workaround to assign this switch to a hardware button. The switch now is moving and the green light is shown. Cheers.

Is your cabin altitude over 10.000ft or you differentiate pressure of scale high? This can happen if you climb fast but climb the cabin to slow.

@roadrunner I am suspecting that my realsimgear is at fault. I'm not prepared to mess around with that for one aircraft that is not working. The funny thing is that this is the only black square airplane I am having trouble with (I have 3 others). Oh well, back to flying something else. Thanks for the help

@mad_x Thanks!!!

Thanks for; The condition lever position can now be controlled via the L:Var L:BKSQ_ConditionLever from 0-2. This should not be necessary, since the condition lever is most easily controlled via the default mixture bindings; however, it was added for convenience.

@mobbe123 I think I got it to work. Some file in the community folder was making trouble.

@randolf Yep It was the fan that was my problem. I didn't use as I thought it was something to do with AC only. Works pretty good now. Thanks!