FSX-SE Control Madness

[zmak 331]

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?

[Bob Scott 7,715]

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

 

[sloppysmusic 194]

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. 

[zmak 331]

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, 2019 by zmak

[airernie 263]

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

[zmak 331]

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?

 

[sloppysmusic 194]

Personally I only use FSUIPC for every hardware control. Makes it simpler having it all in one place. 

[airernie 263]

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.