The one on flightsim seems to have been taken down. A2a has one that came with the Aerostar but it doesn't seem to work any more either. I'm guessing Asobo broke it with SU4.

@Black-Square Sorry Nick, I had to crop the screenshots because 1440 is apparently too big for the forums to handle, and I thought I did a better job describing. And yes, I am in MSFS 2024, which I'm sure I missed saying in the OP. Yes, I have been starting with the propeller feathered, only for the last screenshot with the battery charging and positive instrument air had the propeller out of feather and in the high pitch position. Incidentally, I noticed with the propeller feathered that instrument air and fuel pressure reached nominal levels during startup, and then fell off again. I thought I had been keeping abreast of the propeller RPM issue, but apparently I missed how pervasive it is. Sorry about that. This is the same issue as the generator not being tied to the Ng, and therefore not putting out enough power at lower RPMs?

Hey guys, I don't know exactly how the throttle axis is configured on your TQ6s, but I had good results with my Velocity One quadrant using the MSFS 2024 sensitivity settings. I posted the results here if anyone would be interested in taking a look. This gives me the entire range of forward and reverse travel on one axis and roughly matches the virtual detents with the proper positions on my physical axis, though I don't have physical detents. If you guys have physical detents, this same method should, if I'm understanding it right, allow you to tweak it such that you can match the physical detents to the virtual ones, it might just require a different neutral and Sensitivity+/- settings.

@Mark Appreciate it as always.

For Axis And Ohs I managed it, changing the Interior.xml a bit. At the component ELECTRICAL_Switch_Alternator_1 I added this code: <OVERRIDE_ANIM_CODE> (L:var_GeneratorSwitch, number) 1 == if{ 0 } (L:var_GeneratorSwitch, number) 0 == if{ 100 } (L:var_GeneratorSwitch, number) 2 == if{ 200 } </OVERRIDE_ANIM_CODE> Afterwards I used the "Layout Generator" from fs.to to recalculate the layout.json. Now I'm able to control the Switch using something like 1 (>L:var_GeneratorSwitch, number). @Black-Square It would be great if you could add this to one of the next updates. This was already missing in the 2020 version and drove me nuts.

Thank you very much for your advice - greatly appreciated.

Agreed and the OAT gauge top left. The deg C does not match. Dunno about F.

I've emailed Aeroplane Heaven and your selves at Just flight many many times begging for a Super VC 10 in MSFS 2020-2024 infact so many times in the last six years my emails now get ignored.

@Black-Square said in A list of Squawks as a 10+ year TBM Maintainer: This is the only tough one, unfortunately. As I just explained to someone else in another thread, MSFS does not really have any support for beta range, and everything you see here is me fighting with the underlying simulation to get what I want. For whatever reason, the propeller simulation creates a decrease of RPM when reducing the blade pitch into the beta range. I've considered adding yet another patch of my own on top of this simulation to mitigate the problem, but too many patches on top of patches can become a dangerous thing in software, unfortunately. I have no knowledge about the real aircraft behavior, however would like to add one point from a pure flightsim perspective: It is basically impossible to find a power setting that maintains taxi speed at a stable level. If I control the power lever with the keyboard F2 & F3 I can set increments of 1%. If I have a setting that increases speed, reducing by 1% already slows the aircraft down. If this is similar in the real aircraft I would accept this. If not, I would appreciate checking if the a stable speed can be achieved with a broader range of power lever setting, knowing that aircraft weight & weather conditions have an influence as well. Anyway, @Subsonic many thanks for your real maintenance view, if you can also on my comment.

Is there any connection to the surface modeling from the simulator? I've found similar behavior with another popular 737 previously that once at a set taxi speed, it never changes. I see this as well with the Caravan. If I am in Beta at 15kts - It will tend to stay at 15kts. If BETA is ZERO thrust from the prop, I'd expect some friction and other forces to begin reducing the taxi speed where I will eventually need to pop out of beta to maintain forward speed.

[image: cf01951b-5fe0-4b55-8a65-2577915ea8e5.jpg]

Brilliant, thanks Mark!

Just adding feedback for the 'buzzing' prop while in cruise in latest update. This seems to be a regression from V1.0 as you would not hear this in the actual aircraft. Glad to see it will be corrected! I also notice this issue in the TP Bonanza along with other default MSFS aircraft (TBM comes to mind) You do not hear these prop sounds in-flight, it is only something you would hear on the ground or externally...

@Mark Thanks. I will test it again over easter and see if the problem still exists. I‘ve read that there are some people reporting similar issues with other products and even default aircraft here: https://forums.flightsimulator.com/t/unable-to-click-some-items-with-the-mouse-in-vr/758216/32 Seems to be VR related and probably something for Microsoft/Asobo to solve, not you…

@Black-Square the su5 beta also affected the Baron in VR in a similar way, click spots become very small and the tablet was unreachable. The releases notes did mention they were adjusting the interactions in VR so it wasn't a surprise to me. However it seemed to be fixed in the last update they pushed (within the last two weeks) - for me at least.