TBM 850

@laurreth A further reply from the developer on this for you...

"I'm sorry, I shouldn't have written that post from memory. I checked on the engine performance in the simulator today and the maximum attainable torque at FL300 at ISA is 105%. The maximum performance cruise table that I've been using from the POH indicates that this is the torque available at that pressure altitude with the power lever fully forward. I hope that helps dissuade any fears of undesired performance changes."

Hope that helps.

@voice-of-reason so in the real aircraft the battery doesn't get charged while the engine is running and the generator is on?

For everything not mentioned there: Just have a look into my script collection on flightsim.to. Almost every switch of the TMB 850 is handled there. In case of missing ones just leave a comment.

https://flightsim.to/file/61922/blacksquare-tbm-850-scripts-for-lorby-s-axis-and-ohs-aao

Just simply slowly greying out the whole screen would work for me. I think XPlane 11 did this. You only make this mistake once :)

@voice-of-reason wow, I would have never guessed that. Learned something! Thank you!

@voice-of-reason Thanks for the response!

The RMI very well may not-- I haven't checked any source documents, I was just basing it off the included manual (p.30 in the printer friendly version described a flag).

MSFS does have a Total Air Temperature value integral to the sim that does calculate the ram air temp:

From the SDK:

TOTAL AIR TEMPERATURE Total air temperature is the air temperature at the front of the aircraft where the ram pressure from the speed of the aircraft is taken into account.

Feel free to pass that along-- I'm not sure how the values match up to the IRL TBM's temps.

Thanks again!

@voice-of-reason Thank you for the answer and the support! The TBM is awesome!

A quick reply from the developer for you:

'As I've answered elsewhere, this is a change that has to happen at the soundpack level, so it's not something I can do as a quick fix. I will make sure this gets added to the Dukes, and is added to all my other aircraft when I do updates that include custom sounds in the future. Thank you!'

Hope that helps.

@eker A direct message from the developer for you...

'I wanted to make sure I replied to this thread while I was answering many of these posts with bugs and suggestions. Thank you so much for the positive feedback. As a one-man development team, I know that I cannot make THE best aircraft for MSFS alone, but I strive to create ones that spark a deep sense of joy in me as a real world pilot. I know that my way of doing things may not be for every simulator pilot, but there are definitely some out there whose taste will align with mine, and I hope they thoroughly enjoy my products. Thank you!'

Thank you.

A reply direct from the developer...

I have added an L:Var for the condition lever in the next update, though using a slightly different technique. It will be "L:BKSQ_ConditionLever, number" (0-2).

Hope that's of some help.

@ape42 From the developer:

'This is a limitation of the Asobo rendering engine, unfortunately. Thank you for taking the time to write, though.'

Hope that helps answer that for you.

From the developer...

'Fixed and ready for the update that's coming this week. Thank you! There will also be a very exciting surprise feature involving these static wicks in the next update. Shhhh...'

Hope that helps

Message on this from the developer:

'Thank you for reminding me of my initial reaction of awe to this too! It had been so long since I programmed this that I had completely forgotten about it. Given that it's really so simple, I wonder why I've never seen a physical RMI or HSI unit equipped with a deviation bar. I'm glad my software could entertain you :)'

From the dev:

'I put the starter motor relay on the distribution bus now. Thank you for noticing that. I cannot find any scenario in which the light tests would work with the battery power off, though.'

Hope that helps.

Yes to confirm, a message from the developer:

'This was actually caused by a single typo. I've fixed it for the next update, but if you want to fix it yourself, change the following line in the panel.xml file.'

<NAME>GTN750</NAME> ---> <NAME>GTN750_INT</NAME>

Hope that helps

This is fixed and ready for the update that will be heading your way, in this coming week. Thank you!