Elevator trim tab and rudder animation error
-
Very happy that BKSQ added the moving trim tabs on walk around! I just tested it, but the direction of the trim tab is wrong? From memory when I do walkarounds on my Piper Arrow, when I move the elevator up, the trim tab goes up, and vice versa for elevator down. In this Bonanza, I noticed when the elevator goes up, the tab goes down? Same applies to the aileron trim (also potentially the wrong direction).
Additionally for the rudder, I recall it can only move it a little because the cables are holding it, and if the front wheel is on the ground, there's only so much rudder travel you can put in by hand. And when you check the rudder by hand and you release it, it should go back to the neutral area (aligned with the nose wheel). I understand different aircraft have different rudder-to-nose configuration, so I'm not sure if BKSQ's implementation is accurate.
Can someone confirm both?
-
For the elevator, you are correct, that is how our PA-28's behave, because they have "all-flying stabilators" with "anti-servo" tabs. Anti-servo tabs work in the way you describe, but servo-tabs (what most people just call trim-tabs) work in the opposite direction. Some aircraft have a mix of both types, and some move in conjunction with the main surface, while others hold a static angle relative to the surface at all times. I spent about half a day trying to confirm this functionality for each of my aircraft, but that doesn't mean that I got it 100% right for each one. The TBM was particularly challenging, as it has all three! In this instance, I believe I'm over the target for the Bonanza, but hopefully someone will be able to confirm that.
As for the rudder, you are also correct about our PA-28's. One of the things I like about the PA-28 and related Pipers is that they have very stiff connections between the nose wheel and the rudder, which is why you typically don't need a rudder gust lock for a PA-28. On the other hand, a C172's rudder will basically flop all over, regardless of the nose wheel position. From what I have seen, the Baron and Bonanza exist somewhere in the middle.
However, the lack of centering springs in MSFS is not really related. When you are in walkaround mode, the simulator hard-codes a stop to all control surface inputs. That's why your hardware has no effect when you're in walkaround mode. The typical behavior in Asobo's aircraft is just for the control surface to remain where you left it, which I emulated with my own code for these aircraft. The thought has occurred to me to code my own gravity and centering dynamics too, but then these start to conflict with hardware inputs once you're back in the cockpit, and I'm not sure MSFS 2024 has a fool-proof way for us to detect when you are in the walkaround mode. That being said, it's something that I will keep my eyes out for next time I'm working on walkarounds.
See, this is what happens when you get me talking about real world aviation
I hope that answers some of your questions!
