FSUIPC recognition of the throttle-range

[Kosta]

Hi Pete,

Need your help once again:

My FSUIPC is recognizing the whole range on some axes on my Saitek TQ, and some only as half.

That said, it has always been working, just suddenely out of the blue, since yesterday.

Can't say if I changed something to cause this, nothing I can think of.

I just want to know: is that normal? Basically always my first two axes on the TQ are recognized as 0 to 16384 and my last one as a -16384 to 16384.

Furthermore, I don't want to calibrate in FSUIPC, due to known problems with NGX.

Problem is: I'm using 2 TQs, and from 6 axes, I'm using two middle ones for Throttle 1 and 2 respectively.

T1 is working OK. T2 is working only from about 80% N1, basically having a different range.

In windows, both axes show up the same.

When I try calibrating them, I can't do it with the "send axis to FS directly".

EDIT: Ahhh, search is my friend.

[Pete Dowson]

My FSUIPC is recognizing the whole range on some axes on my Saitek TQ, and some only as half.

That said, it has always been working, just suddenely out of the blue, since yesterday.

Where are you seeing this? Do you mean the INput numbers don't change on half of the lever's range? If FSUIPC sees no change arriving from the device (or its driver) then obviously it cannot do anything with it. It has no control over what comes in.

If you mean the output FROM FSUIPC to the sim, then it's to do with your calibration or other settings.

I just want to know: is that normal? Basically always my first two axes on the TQ are recognized as 0 to 16384 and my last one as a -16384 to 16384.

If that's on input then it is your device or its driver. If you mean on output, then remember that "THROTTLEn_SET" controls only have positive values for forward thrust, negative means reverse, whilst the standard FS controls, AXIS_THROTTLEn_SET, only have forward thrust for all values, with -16384 being idle.

Furthermore, I don't want to calibrate in FSUIPC, due to known problems with NGX.

I don't think it is the use of FSUIPC calibration which gives problems. the known problem is that it doesn't like THROTTEn_SET controls which FSUIPC's calibration normally uses. You can get around that by using the NRZ (no reverse zone) option, and setting "UseAxisControlsForNRZ=Yes" in the appropriate section of the INI file.

When I try calibrating them, I can't do it with the "send axis to FS directly".

You surely mean the option to send to FSUIPC directly. The NGX wants to see the FS controls I think.

EDIT: Ahhh, search is my friend.

http://forum.simflig...__fromsearch__1

Ah, so was trhe first problem the Saitek registry bug?

Pete

[Kosta]

Yes yes, the Saitek bug, exactly that. Now all throttles show again as full range.

But, I have another problem, which I am trying to fight now:

in FSUIPC4.ini there are:

[JoyNames]

AutoAssignLetters=No

0=SideWinder Force Feedback 2 Joystick

0.GUID={6069C4D0-57D1-11DF-8001-444553540000}

1=Saitek Pro Flight Rudder Pedals

1.GUID={373E4120-767A-11E1-8001-444553540000}

2=Saitek Pro Flight Throttle Quadrant (USB)

2.GUID={37408B10-767A-11E1-8002-444553540000}

3=Saitek Pro Flight Throttle Quadrant (USB)

3.GUID={37408B10-767A-11E1-8003-444553540000}

4=Logitech G13 Joystick

4.GUID={DC6A74B0-5F42-11E1-8004-444553540000}

5=PFC Yoke

5.GUID={0AA06970-64A2-11E1-8001-444553540000}

They should be:

[JoyNames]

AutoAssignLetters=No

0=SideWinder Force Feedback 2 Joystick

0.GUID={6069C4D0-57D1-11DF-8001-444553540000}

3=Saitek Pro Flight Rudder Pedals

3.GUID={373E4120-767A-11E1-8001-444553540000}

1=Saitek Pro Flight Throttle Quadrant (USB)

1.GUID={37408B10-767A-11E1-8002-444553540000}

2=Saitek Pro Flight Throttle Quadrant (USB)

2.GUID={37408B10-767A-11E1-8003-444553540000}

4=Logitech G13 Joystick

4.GUID={DC6A74B0-5F42-11E1-8004-444553540000}

5=PFC Yoke

5.GUID={0AA06970-64A2-11E1-8001-444553540000}

How do I force those numbers in front to stay? This would mean I would have to do all my assignments all over again (a MAJOR pain in the ass).