@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 have the same problem. The new installer doesn't even allow me to pick a different install location.

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.

thanks. I finally solved it by using the same as I use for the FSR500. Button 24 on Bravo. Button Pressed Send THROTTLE1_DECR - event Delay execution for 200 ms (repeat 5 times) Button released Send THROTTLE1_cut - EVENT Works great in the Van !

I understand there may be higher-priority updates, but I think this particular feature deserves attention. The shader-based prop animation introduced in msfs24 is, in my view, a significant step forward. It removes that harsh and unrealistic transition between a static propeller and a spinning one, which has always been visually jarring. Beyond just looking smoother, it adds a real sense of volume to the prop disc—both from external views and from inside the cockpit. The way it interacts with lighting is also a big improvement. Reflections from the sun and other light sources feel much more natural, which enhances overall immersion.

So now I had time to check - sorry it was my bad. Too stupid question. In the failures tab there was activated "1x Realtime" and so I had a failure with this compressor. I did not expect this. But now I know that I should check this each time I fly. I love the study level details of your aircrafts....was just too stupid to realize this.