TBM 850

I know I will not be able to convince you but I will share my feedback too.
I found the saves more consistent in the Duke than in previous aircrafts, I don't know if it's the fact that avionics is selected from tablet and not a switch anymore or if the state saving part has been redrawn.
Anyway, so far I didn't had avionics being reset and found its saves pretty solid.

Maybe wait to see for the tablet to be incorporated into the TBM and see if you come across this issues again.
I hope your opinion will change and be able to notice as I did some improvement.

Also for your information, I've just completed the same leg with the Turbine Duke and it works fantastic.

you are welcome, it s always a pleasure to help ! :0)

@Black-Square said in Some technical inaccuracies:

One might think that I would become irritated with such nitpicking on my products, but to the contrary

All your products are so close to perfection... all we have left is nitpicking. 🙂

Thanks for explanation, maybe I will start pestering Working Title. I dont use the GTN750 at all, prefer the older instruments, but nevertheless, it still happens too often. Great pity to have relatively expensive payware and get these problems.

Actually, I also see that the aircraft dont always save their current state on shutdown. I usually go back to cold and dark, with G530/430 chosen. But on restart, the GTN750 bezel is present, will see if I get a plan to load when aircraft loads G530, from cold.

Is it possible to force a particular loading configuration in the aircraft configuration file??

@Black-Square Thank you for your kind words. I really enjoy the work you have done with the TBM and fly pretty much exclusively on Pilotedge (ATC Network) with the aircraft daily. I fly by the book and treat the aircraft as if it were a real airplane and what I would do in the real world. Furthermore, I have to say it comes really close to the numbers of the real TBM850 POH which I use for this aircraft and it's very impressive, despite the turboprop limitations within MSFS. Awesome job!

As far as testing goes, I have tested the engine conditions and failures further in flight and can confirm everything is working the way it should, just purely state saving being an issue upon reload with the engine, which explains why I haven't been seeing a decline in engine health upon reloads.

I will continue to fly and will just overlook the shortcomings with the state saving system in place, now that I understand what is going on. I will be eagerly keeping an eye out for your update. Thank you for your continued support on the TBM. Looking forward to the Duke!

You could check settings of your gps device to see what types of messages you have enabled and maybe disable those you don't need like airspaces, traffic, etc.

Glad to hear it's working well for you. Just for anyone else reading this, what I do about this is just to jostle my hardware throttle, even the smallest amount, after touchdown if I have any question of the virtual throttle position.

To answer your question, yes, it's possible in many PT6A powered aircraft, however, it is also prohibited by the operating limitations of almost all these aircraft. The only one that comes to mind where this is not prohibited is the Pilatus Porter. I've seen it done with Caravans in real world skydiving operations, but it is still prohibited by the POH, and the limitation placarded on the panel. The problem is usually overspeeding of the propeller, since beta is the opposite of feather, if that helps you think about it. I make no guarantees of how my aircraft will behave in this configuration, especially with respect to propeller speed, but I can say that they will slow down REALLY fast if you do try it.

@Black-Square said in Binding, H-events and other information:

VsSwitch:

Hi, the VS switch is still giving me headache. How would I implement that with FSUIPC..? Via LUA?

Yep, I use the WT GNS530. Thanks for having passed the info if it is for them to solve then 👍.
And thanks again for your great work, keep it going 😉

Hi Nick,
For me the problem seems to have disappeared. I have no clue what cured the issue. Perhaps an MSFS update. I also use AutoFPS now, but I do not think this played a role.
Best regards,
Harry

@Black-Square

Thank you for the response, I'll consider if it's needed by any other add-on and potentially remove it.

Looking forward to the Duke, the TBM has quickly become one of my favourite things to fly in the sim. Great work :)

You are correct. Bus number 3 is the main distribution bus in the TBM. That would generally be the best to measure, but if you're looking for the specifics before I publish an update soon, then you can find what each annunciator light is connected to by searching for "VOLTAGE_SENSE_BUS" in AnalogTBM.XML.

I think I already implemented that fix for a future update. If you want an immediate solution, you can also change

this.tempUnit = false;

to...

this.tempUnit = true;

in FreeAirTemp.js in...

...\bksq-aircraft-tbm850\html_ui\Pages\VCockpit\Instruments\Generic\Misc\bksq-aircraft-tbm850\FreeAirTemp

Very interesting! Thank you for making that video and explaining what you've seen. Does this happen with all the controls in the cockpit, or is it just those two? I've seen YouTubers who use lots of windows in VR with no problem, so I'm sorry that you're one of the unlucky ones.

Unfortunately, I still think this is very unlikely to be anything related to my aircraft, but I want to help you in any way I can. Please keep me updated if you learned anything else. Usually I have some recommend Discord server or forum for people to take their issues to, but this is an usual one. Are there any VR specific communities for MSFS that you might be able to ask?

Just to answer your question, sometimes the animation system can get stuck and not take any inputs, literally if your camera is looking one direction. Sometimes this happens to me while developing, and I have to restart the simulator. You can look directly at the panel, and nothing will work. Look out the side windows, and suddenly all the animations will catch up with any changes you've made. Look back forward, and everything will get stuck again. I don't think that's what you're seeing here, but it's possibly related.