FSX Joystock control vs FSUPIC control

[wade1]

HI I am building a research based simulator using FSx ( acceleration ) . The problem i am having is that i am having a bit of joystick lag with FSX controlling my joystick, I have a registered up to date version of FSUIPC installed , I have used the rescan method to find the joystick axes and calibrated them using fsuipc calibration successfully . The problem is as soon as i disable the joystick or delete the joystick axes in FSX settings. FSX doesnt doesnt pick up the joystick even though FSUIPC still registers the axes so i end up with no joystick control With the joystick re-enabled in fsx settings and registered on fsupic axes i can tell that FSUIPC and fSX are fighting for control for teh joystick and there is unusual movement and lag when flying the aircraft.

it is driving me crazy cos FSUIPC looks like a far better way to calibrate and provides more sensitivity to the joystick controls.

Is there some setting i can change in the fsx.cfg or fsuipc.ini ??/ that would help

My joystick is a simple potentiometer based copntrol column going through a haagstrom encoder board which provides three basic axes x, y, z(rudder) . and registers as a simple joystock in control panel and FSX.

Really need a definitive answer in this one so your help would be greatly appreciated ..

BTW i have tried a standard microsft joystick and the same effect occurs so its not the joystick

[Pete Dowson]

I have used the rescan method to find the joystick axes and calibrated them using fsuipc calibration successfully.

Does that also mean you assigned them in FSUIPC? I'm not sure why you mention "rescan" but not "assignment", which is much more important.

The problem is as soon as i disable the joystick or delete the joystick axes in FSX settings. FSX doesnt doesnt pick up the joystick even though FSUIPC still registers the axes so i end up with no joystick control

Ah, that seems to answer the question then. You haven't assigned them in FSUIPC. "Rescan" means nothing on its own. If you have no axes assigned in FSX or in FSUIPC then they obviously cannot do anything.

With the joystick re-enabled in fsx settings and registered on fsupic axes i can tell that FSUIPC and fSX are fighting for control for teh joystick and there is unusual movement and lag when flying the aircraft.

No, you can't have it both ways.

My joystick is a simple potentiometer based copntrol column going through a haagstrom encoder board which provides three basic axes x, y, z(rudder) . and registers as a simple joystock in control panel and FSX.

In that case it is a simple matter of assigning either in FSX or FSUIPC. There really isn't going to be that much difference as long as, for FSX assignment, you change the sensitivity mode as described in the FSUIPC calibration documentation. I suspect some part of what you don't like about FSX's axis treatment is that by default it is based on time differences not on the direct linear values from the axis.

No matter how you assign you can still calibrate in FSUIPC if you wish.

There are also two ways of assigning in FSUIPC -- to the same FSX controls which FSX would assign to, or direct to FSUIPC calibration. The latter is more efficient, but I'm not sure you'd notice the difference very much.

You sound rather confused, and maybe unable to explain yourself adequately? Please try to be more explicit about what you've actually done -- or if you cannot, show me the [Axes] and [JoystickCalibration] sections of the FSUIPC4.INI file so I can see for myself.

Regards

Pete

[Bob Church]

Hi Wade1,

PMJI, you might also check your frame rate when the stick starts to lag. Compared to the speed of the data through FSX, FSUIPC, etc., the frame rate has a far greater effect on axis/button lag than anything else. I've had perhaps 100 emails over the years from people whose "joysticks work great until they get near the ground". How would the joystick even know what the altitude was?

What happens is that they've come down into ground clutter, usually on landing, and the frame rate drops rapidly while it generates the extra details. I've seen it drop from 50-60 FPS to 5-10 FPS going from blue sky to airport detail, and you can certainly feel that in the controls since they are only updated once per frame.

If that's the case, the only fixes I know of are lower detail settings or fast CPUs and Video cards. Keeping the Frame Rate above 20 FPS is usually good, 10 FPS gets kind of unpredictable, less than that and it can get to be nearly impossible to make a smooth approach or avoid overshoot.

Best regards,

- Bob

The StickWorks

http://www.stickworks.com

[wade1]

Hi Pete yes perhaps i didnt explain correctly , when you say assign the axes in fsuipc i assumed that this is the procedure/.. this is what did i pushed rescan moved the aileron axis and up popped the x axis , and i moved it full range and got a digital readout from fsuipc i then selected "send to fsuipc calibration" then i pushed rescan again and moved the elevator and up popped the y axis in the little box and moved it up and down and got a digital range readout from fsuipc i then selected once again "send to fsuipc calibration" Then i went to fsuipc joystick calibration and calibrated both axes in fsuipc . I assumed that is how the axes get assigned in fsuipc is there some other step that i am not aware of??? that has to be done ???? even after doing this procedure when I disabled the joystick in the FSX settings i get NO movement in FSX from fsuipc calibrated joystick ECEN THOUGH when i go back to fsuipc it is still registering the joystick in the fsuipc joystick calibration . Is there some extra step in fsuipc of assignimg the axes that has to be done..

It is very frustrating as i am following the fsuipc guide as closely as possible and i cannot understand why FSx is mot picking up the my FSIPC calibrated joystick

Does that also mean you assigned them in FSUIPC? I'm not sure why you mention "rescan" but not "assignment", which is much more important.

Ah, that seems to answer the question then. You haven't assigned them in FSUIPC. "Rescan" means nothing on its own. If you have no axes assigned in FSX or in FSUIPC then they obviously cannot do anything.

No, you can't have it both ways.

In that case it is a simple matter of assigning either in FSX or FSUIPC. There really isn't going to be that much difference as long as, for FSX assignment, you change the sensitivity mode as described in the FSUIPC calibration documentation. I suspect some part of what you don't like about FSX's axis treatment is that by default it is based on time differences not on the direct linear values from the axis.

No matter how you assign you can still calibrate in FSUIPC if you wish.

There are also two ways of assigning in FSUIPC -- to the same FSX controls which FSX would assign to, or direct to FSUIPC calibration. The latter is more efficient, but I'm not sure you'd notice the difference very much.

You sound rather confused, and maybe unable to explain yourself adequately? Please try to be more explicit about what you've actually done -- or if you cannot, show me the [Axes] and [JoystickCalibration] sections of the FSUIPC4.INI file so I can see for myself.

Regards

Pete

[Pete Dowson]

...this is what did i pushed rescan moved the aileron axis and up popped the x axis , and i moved it full range and got a digital readout from fsuipc i then selected "send to fsuipc calibration" then i pushed rescan again ...

So you never actually assigned to any control in the drop downs? Those are the 4 places BELOW the option you stopped at, to allow up to 4 assignments for each axis.

If you don't assign an axis, how do you think FSUIPC will know what you want to do with it? selecting "Send to FSUIPC calibration" simply selects the METHOD of it being sent, not WHAT you are sending!

Why not read a little more of the User Guide? It would help/ There are even some pictures illustrating things for you.

I assumed that is how the axes get assigned in fsuipc

Why ASSUME anything at all when it is all documented? Why skip most of the important parts of the document in order to frustrate yourself and come here to waste so much more time than you would spend by just looking things up? I don't understand.

Is there some extra step in fsuipc of assignimg the axes that has to be done..

It is NOT an "extra step". You are omitting the MAIN step -- the actual assignment! I really don't understand how you could possibly miss it. This is the single most important step in assigning an axis -- the actual selection of the function to be performed! :-(

It is very frustrating as i am following the fsuipc guide as closely as possible and i cannot understand why FSx is mot picking up the my FSIPC calibrated joystick

It won't pick up anything if the axis is not assigned.

:-(

Pete

[wade1]

good point peter i must have had a brain fade i did this process in the past when i was playing with the throttles but completely forgot about it this time thanx for your help i will give a try and see if it cures my joystick problem .cheers mate most appreciated