May 10, 20251 yr Not able to ask questions yet on their discord channel and the only issue I'm having w/ this plane which I just bought 2d ago is an alert re the left flight stick needing null zone calibration or something along those lines. In the MCDU on the controls config page related to the sidestick there is no 'calibration' option but you can enter a % null or I guess dead zone. If I move my TM Pendulum Yoke in all directions fully while on that page the alert disappears, but then reappears when I relaunch the plane for a new flight. Is this an error or just a prompt to check controls? The plane is so similar to FBW's 320nx that the learning curve is pretty flat and I've had no issues flying the plane, just this alert. The plane does feel very polished and wants to exploit the GPU considerably more than any other plane I am using, but it's also totally smooth and stutter-free. Noel System: 9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL 64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync. Aircraft used in MSFS 2024: Fenix A320, Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.
May 10, 20251 yr I encountered this issue as well when I first used the Fenix, using a Thrustmaster flight stick for aileron and elevator control. When I entered the controls configuration page of the MCDU, I found that I was getting an errant downward input to the ailerons that caused this error message to appear repeatedly. In my case, I also had a CH yoke plugged into my system while using the flight stick to control the Fenix. My guess is that you might also have another controller in use that also can provide aileron or elevator inputs, and this is interfering. You could perhaps solve the problem by unplugging the other controller. In my case, I use the CH yoke’s buttons and toggle switches generally for many aircraft so I want to keep it plugged in. The solution for me was to create a distinct profile for the CH yoke that deletes the aileron and elevator axes, and use this profile when I am running the Fenix with the flight stick. No more stray aileron inputs and no more controller error messages from the Fenix. Rich
May 10, 20251 yr Just a quick correction - I was getting an errant downward input to the elevator, not ailerons. Deleting the aileron and elevator axes would solve either an errant aileron or elevator input
May 10, 20251 yr I think the message appears if stick or yoke doesn't quite go back to dead centre when resting. You can increase the deadzone in MCDU control config. I never got this message with my old plastic VKB stick. Bought a new heavy metal VKB stick and the message was appearing. The stick came with a big selection of springs and I replaced the weak default springs with stronger springs which stopped the message appearing.
May 10, 20251 yr Author Thanks y'all. I don't think it's another input as I don't have another controller beyond the pendulum yoke that would do that. So I guess it's not a built-in method to check controllers. This yoke is super tight and in the SIDESTICK config both pitch and roll go back to 00.00% when at neutral. I do have null zone set at 3%. I did find the CLR button so made the message disappear that way, FWIW. Odd though no good explanation still. I do have incremental trim set on my TQ, could that play a role perhaps? Noel System: 9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL 64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync. Aircraft used in MSFS 2024: Fenix A320, Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.
May 10, 20251 yr I think if you go into the MCDU settings for the stick/yoke and fully exercise the controller to all of its limits, the message goes away. i7 12700K , DDR4 64GB RAM @3600MHz, Asus Z690-Plus D4 MB, Gainward 4090 RTX Graphics, 850W Corsair PSU, Kraken AIO watercooler, Nvme 1TB ssd, 1TB ssd, 500GB ssd.
May 10, 20251 yr Check in your settings for any key bindings etc on control surfaces. That’s what gave me that master caution.
May 10, 20251 yr 2 hours ago, Noel said: Thanks y'all. I don't think it's another input as I don't have another controller beyond the pendulum yoke that would do that. So I guess it's not a built-in method to check controllers. This yoke is super tight and in the SIDESTICK config both pitch and roll go back to 00.00% when at neutral. I do have null zone set at 3%. I did find the CLR button so made the message disappear that way, FWIW. Odd though no good explanation still. I do have incremental trim set on my TQ, could that play a role perhaps? There's a little bit of noise in my Saitek X-56 stick, otherwise it's a great piece of kit. Unfortunately, since release day, the Fenix has thrown this message, I've never gotten it to go away with nullzone tweaking, and the official Fenix line on this is basically "oh darn sounds like a problem you're having." It's very annoying. I'll be on the climb out, everything looking great, and then the plane throws a master caution and it's this. Much ado about nothing.
Create an account or sign in to comment