January 8, 20197 yr Hi guys, wondering if anyone else came across this issue. Seems very weird and I have tried everything I can think of to remedy. Basically if I am in any aircraft sitting still I have full rudder and steering movement. Once I start to taxi it’s like the rudder pedals lock up and will not do anything. Looking at the pedals shows very slight movement. So basically the only way to steer is to use the toe brakes or set up the steering tiller axis in FSUIPC. I use a CH eclipse yoke with Saitek rudder pedals. 1. Same issue with A2A 182 and Cherokee, Majestic q400, and default Maule. These are the only ones I have tried but assume it effects all aircraft. 2. Auto rudder is unchecked 3. Have tried mapping controls in P3D and FSUIPC. Disabled controllers in P3D when mapping with FSUIPC. 4. Have verified I don’t have any conflicting axis assignments. 5. Have recalibrated controls about 500 times. Each control axis shows full and normal range. 6. Does not matter what controller is used. Have tried pedals on Eclipse yoke, rudder pedals, and my old joystick. 7. Tested in Xplane and everything is normal. 8. Issue seemed to start shortly after I installed my new CH eclipse yoke. I was having issues setting up my PTT button for pilot edge and had to install the CH manager software to make PTT work correctly. Did not have this issue with old Saitek yoke. 9. It acts like something in the sim is telling it to lock up the pedals when I start to move. But if u come to a complete stop pedals work normally again. I am at a loss guys. Any help is appreciated! Matt Wilson
January 8, 20197 yr Check the P3D axis assignments on ALL controllers (including devices like gamepads) and make sure you don't have a "phantom" axis assignment. Make sure you don't have an unintended tiller axis assignment defined in FSUIPC. Try selectively disabling any/all modules that affect axes/flight controls (Accu-feel, FSUIPC, CH Manager etc). Regards Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
January 8, 20197 yr Author 4 minutes ago, w6kd said: Check the P3D axis assignments on ALL controllers (including devices like gamepads) and make sure you don't have a "phantom" axis assignment. Make sure you don't have an unintended tiller axis assignment defined in FSUIPC. Try selectively disabling any/all modules that affect axes/flight controls (Accu-feel, FSUIPC, CH Manager etc). Regards Thank u! Rechecked every axis on every control in FSUIPC and found another rudder axis assigned to the throttle on my joystick. I have no idea how that happened! All good now Matt Wilson
Archived
This topic is now archived and is closed to further replies.