March 16, 20197 yr I know its just something simple but Im stumped. After a long reinstall week of windows and fsx-se all of a sudden Controls are acting weird. scenario 1 FSX-SE settings/ controls / Enabled controllers box is TICKED..../ control axis TICKED.....the plane is all over the place and only responds to some yoke inputs Scenario 2 Enable controllers UNTICKED...flys like a dream except of course I cant use the rest of the settings eg panning, trims, flaps or anything else etc etc etc Whats that all about? ZORAN
March 16, 20197 yr Sounds like you have one or more phantom axis assignments. Check the axis assignment page in the sim for ALL of your listed controllers, including devices like game controllers/gamepads, and make sure FSX didn't make unintended axis assignments on those devices. 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
March 16, 20197 yr Bob is spot on. Sometimes it's best to delete all the assignments in the axis section then add them back manually one at a time then SAVE a preset with the working assignments. Russell Gough SE London
March 16, 20197 yr Author Thanks guys. Seems Ive made some progress. I hit reset all defaults and checked fsuipc and for some reason even though there is no profile assigned to the default planes I was testing, the axis were registering with fsuipc so I deleted all that and now when the I uncheck the controllers box the plane no longer responds which is the way it should be so fsuipc phantom axis was the problem HOWEVER.. now a new problem. The planes Im testing only respond to control input in slow motion. All axis are in slow motion ...why?? lol Checked to see simulation rate and its normal. took a full 12 seconds to to hit 20deg pitch up I will try to reset all axis like suggested and take it from there edit. Pmdg fly perfect with fsuipc. Anything fsuipc works but default axis default planes are still a bit jerky in movement and cant be flown in slow motion. Not that it matters I guess as I dont fly default but its just to weird Edited March 16, 20197 yr by zmak ZORAN
March 17, 20197 yr Confused by 'default axis'. Do you have some aircraft using axis defined within FSUIPC and some using axis defined within FSX? IMHO, control axis definitions should be 100% FSUPIC or 100% FSX, but not a mix, I assign each class of aircraft a separate profile in FSUIPC, exp; ASEL, AMEL, iFly_737 ERJ_175-195, QW_757, etc. It may be overkill, but it allows me to assign different functions to an axis without conflict. Ernie
March 17, 20197 yr Author 17 minutes ago, airernie said: Confused by 'default axis'. Do you have some aircraft using axis defined within FSUIPC and some using axis defined within FSX? IMHO, control axis definitions should be 100% FSUPIC or 100% FSX, but not a mix, I assign each class of aircraft a separate profile in FSUIPC, exp; ASEL, AMEL, iFly_737 ERJ_175-195, QW_757, etc. It may be overkill, but it allows me to assign different functions to an axis without conflict. Ernie I agree and I worked it all out. Just deleted the FSX axis and now have all my planes using FSUIPC axis only. I knew the solution was simple but being away from the PC for 4 months and just did a major windows and sim reinstall my brain was fried. Do you have everything going through FSUIPC eg hat switch , views,flaps etc or do you let FSX take care of that and just assign the axis to FSUIPC? ZORAN
March 17, 20197 yr Personally I only use FSUIPC for every hardware control. Makes it simpler having it all in one place. Russell Gough SE London
March 17, 20197 yr 8 hours ago, zmak said: Do you have everything going through FSUIPC eg hat switch , views,flaps etc or do you let FSX take care of that and just assign the axis to FSUIPC? Everything, except the Xbox 360 controller I use for ChasePlane and that is only defined in ChasePlane.
Archived
This topic is now archived and is closed to further replies.