@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.

The state saving in the 146 is not tied to a specific variant or livery. Whatever state is saved when exiting a flight in the 146 will be the same state that is loaded on the next flight in any 146. The only exception to this rule is the configurable equipment (HF aerials, VH3 aerial, etc.), which is automatically configured on a per-livery basis. Mark - Just Flight

@FlightEngineer1 Thanks for your input. As an old real-time industrial automation engineer, I really wish they'd expose the tuning parameters in real-time, so those of us who truly understand how to tune a PID loop using one of the formal methodologies (aka "the right way"), as opposed to just guessing, winging it, or using the defaults as so often seems to be the case with some other aircraft. </rant> Edit to add: and they've been missing filter constants forever. Geez.

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

I gave in - should've held off.

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…

Turn the knob on the amm/voltmeter on the left side to the Gen and Alt positions and show screenshots. I mixed up the above screenshots and didn't realize one was saying PWR ON, I thought it was OFF and INOP, so unless the generator is failed, which I doubt given that you've been looking at the failure screen, I'm curious what the generator and alternator power draws are.

@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.

@Black-Square EGDR Runways 18 & 24 have their signs swapped as well.

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.

Thanks, that's at least confirmation that it's not a user-specific issue.

@fosl yup, same, that's why it's weird

Oh OK - that's what Chat GPT said I should look for in the config file and adjust :).

No I didn't know that, thanks for bringing it to my attention.