aileron and elevator calibration

[dazzan]

Hi Pete

I use FSUIPC 4.062 with FSX.

I have assigned aileron an elevator axis in FSUIPC

to send values directly to FSUIPC calibration.

The problem is that the elevator and aileron

axis move too easily and too sensitive even when using

slope 15 for both and assigning a large space for

neutral position.

I also added to FS.cfg "Stick_Sensitivity_Mode=0"

under controls.

I tried in FSX axis assignment to delete

elevator and aileron axis assignment, but then there

are no values alo in FSUIPC calibration.

So I have to keep the axis assignment in FSX

to get FSUIPC calibration to work.

I use in FSX calibration full sensitivity (100%)

but no neutral zone.

Many thanks for helping

Gilles

[Pete Dowson]

I have assigned aileron an elevator axis in FSUIPC

to send values directly to FSUIPC calibration.

The problem is that the elevator and aileron

axis move too easily and too sensitive even when using

slope 15 for both and assigning a large space for

neutral position.

Erin the extreme that would mean they would virtually not move at all over most of the range of the stick, so I really don't understand how you can get them "moving too easily".

I tried in FSX axis assignment to delete

elevator and aileron axis assignment, but then there

are no values alo in FSUIPC calibration.

In that case they are not actually assigned in FSUIPC's axis assignments. You cannot have them active in both places and assume they will work. If the axes are assigned in FSUIPC's Axis assignments dialog for direction to FSUIPC's calibration, the Calibration part will show "direct" for that axis. If it doesn't then you've not actually assigned them.

Were you using FSUIPC's axis assignments before version 4.062? You do realise that 4.061/2 have experimental DirectInput changes included, and were placed here for testing?

You should know that there's a problem of them not "sticking" in 4.062 (see http://forums.simflight.com/viewtopic.php?t=58407 ) unless you do a scan each FSX session. I now have confirmation that this is fixed in 4.063 which I'll post here later today.

Regards

Pete

[dazzan]

Thanks Pete

I will try 4.063