What is axis 17?

[Kosta]

In my INI, I have axis "17" reappearing all the time. I neither assign it or anything, but it is coming back all the time.

[Axes]

0=17X,256,D,4,9,0,0

1=17Y,256,D,10,0,0,0

2=17Z,256,D,5,17,0,0

3=17R,256,D,18,0,0,0

4=17U,256,D,6,13,0,0

5=17V,256,D,14,0,0,0

And in my profiles, it gets automatical assignments.

What is this?

[Pete Dowson]

In my INI, I have axis "17" reappearing all the time. I neither assign it or anything, but it is coming back all the time.

...

What is this?

Axes 17-19 are either real PFC serial port connected devices with my PFC or PFCFSX driver, or "virtual" axes being injected into fSUIPC from add-on software or plug-ins via offsets 3BA8-3BC4. If oyu haven't installed such drivers, seems you have some other add-on writing to those offsets?

Regards

Pete

[Kosta]

I have PFC hardware, and your dll in the folder for the PFC yoke, pfchid.dll. It it not serial though, but USB. I have both yoke and TQ console.

Nevertheless, they are assigned differently,

Y=PFC Yoke << MISSING JOYSTICK >>

Y.GUID={F8DCACA0-F0A4-11E1-800D-444553540000}

Q=PFC Throttle Quadrant Console << MISSING JOYSTICK >>

Q.GUID={C5DA1150-13D9-11E2-8001-444553540000}

(they are currently not connected, so this is why they are missing...)

and then...

[Axes.Default Cessna 172]

9=YX,256,F,65763,0,0,0

10=YY,256,F,65762,0,0,0

0=JX,256,F,65763,65868,0,0

1=JY,256,F,65762,65867,0,0

2=JR,256,F,65764,65869,0,0

3=RX,256,F,66387,0,0,0

4=RY,256,F,66388,0,0,0

5=RR,256,F,65764,0,0,0

6=AZ,256,F,65765,0,0,0

7=BX,256,F,66292,0,0,0

8=BZ,256,F,66534,0,0,0

11=17X,256,D,4,9,0,0

12=17Y,256,D,10,0,0,0

13=17Z,256,D,5,17,0,0

14=17R,256,D,18,0,0,0

15=17U,256,D,6,13,0,0

16=17V,256,D,14,0,0,0

Y=Yoke

J=Joystick

R=Rudder Pedals

A,B=Saitek TQ

Console is not assigned for default Cessna.

But I do use it with the NGX:

[Axes.PMDG Boeing 737 NGX]

4=QX,256,D,28,0,0,0

5=QX,B,0,16383,65585,0

6=QZ,256,F,66382,0,0,0

7=QR,69,D,42,0,0,0

8=QR,U,-16037,-15102,65972,0

9=QU,36,F,66420,0,0,0,*-1

10=QU,B,16348,16383,65967,0

11=QV,69,D,41,0,0,0

12=QV,U,-16005,-15041,65967,0

13=QS,35,F,66423,0,0,0,*-1

14=QS,B,16348,16383,65972,0

15=QT,256,D,23,0,0,0

19=YX,256,F,65763,0,0,0

20=YY,256,F,65762,0,0,0

0=JX,256,F,65763,65868,0,0

1=JY,256,F,65762,65867,0,0

2=JR,256,F,65764,65869,0,0

3=JS,256,F,65765,0,0,0

16=RX,256,D,7,0,0,0

17=RY,256,D,8,0,0,0

18=RR,256,D,3,0,0,0

21=17X,256,D,4,9,0,0

22=17Y,256,D,10,0,0,0

23=17Z,256,D,5,17,0,0

24=17R,256,D,18,0,0,0

25=17U,256,D,6,13,0,0

26=17V,256,D,14,0,0,0

Nevertheless, the axis 17 appears here too.

Do I understand that I should remove the pfchid.dll if I have USB PFC hardware? I don't need it? I thought I did...

[Pete Dowson]

I have PFC hardware, and your dll in the folder for the PFC yoke, pfchid.dll. It it not serial though, but USB. I have both yoke and TQ console.

Ah. PFCHid.dll is intended for their USB consoles, primarily to drive all the switches and so on. The auto-assignments you are getting are for the quadrant only.

Do I understand that I should remove the pfchid.dll if I have USB PFC hardware? I don't need it? I thought I did...

Quite honestly, I don't know. Are there instructions with it?

The console I have is the Cirrus Pro. You need it for that. I don't know all their products and variations. Does yours have switches etc assigned automatically, via PFCHid, or are you seeing them and assigning them in FS or FSUIPC? If you don't install PFCHid does it all work? Seems like the axes should at least from your assignments above. Do the axis 17 ones respond in the axis assignments if you "ignore" the "Q" joystick ones? I think if I remember rightly, with PFCHid reading the quadrant you're supposed to assign to the axes it sees, these joystick 17 ones, else it assumes a default quadrant, a twin turbo or something. I'd have to check.

Regards

Pete

[Kosta]

So far I know, all my axes are recognized as "Q", as that is how I have it configured. But I will check if they get recognized without the dll, when I get the chance.

There are no special instructions on how to configured, PFC only said plug and play, configure via FSUIPC.

[Pete Dowson]

There are no special instructions on how to configured, PFC only said plug and play, configure via FSUIPC.

In that case they are probably standard USB joystick type devices and don't need PFCHID. The USB devices PFCHID is designed to support only partially look like joysticks to Windows / FS..

Pete

[Kosta]

Alright Pete, thanks for the help!