BU0836 and more then 5 Axes FSUIPC

[CCTFlusi]

Hi,

yesterday i installed my new homebuild yokesytem to my additional centre pedestal/throttle quadrant. Now i got big problems with FSUIPC. It just can handle 5 of the 6 axes. I tried a lot till i noted that the problem is the 6th axes.

I use a BU0836 usb interface, which worked perfect with FSUIPC till today. Also in the XP calibrating programm all axes working very fine. FS2004 also can use all 6 axes but not FSUIPC. And i can't believ that this great tool can't handle that.

Hope someone can tell me where the fault is. I read the manual 5 times without finding anything helpfull.

Cheers

Nils

[Pete Dowson]

Hi,

yesterday i installed my new homebuild yokesytem to my additional centre pedestal/throttle quadrant. Now i got big problems with FSUIPC. It just can handle 5 of the 6 axes. I tried a lot till i noted that the problem is the 6th axes.

I use a BU0836 usb interface, which worked perfect with FSUIPC till today. Also in the XP calibrating programm all axes working very fine. FS2004 also can use all 6 axes but not FSUIPC. And i can't believ that this great tool can't handle that.

FSUIPC3 can, like all of its predecessors, only handle joysticks through the Windows "joy" API. This provides for 32 buttons, 1 POV and 6 axes (XYZRUV).

This interface is simple and efficient and was used by everyone until the invention of the over-enginerred, over-complex, and rather slow "DirectInput". Even FS, when it used DirectX for other things like the screen, still used the old joy interface until, I think, FS2002.

The DirectInput interface can handle up to 64 buttons, 4 POVs (my names PQMN) and 8 Axes (XYZ Rz Rx Ry, S1, S2 which I name XYZRUVST).

I changed FSUIPC's axis assignment facilities over to DirectInput during the re-write made necessary by FSX, so FSUIPC4 supports 8 axes and 4 POVs (as axes), but still uses the older "joy" API for the buttons (so, only 32) and 1 POV (as 8 buttons). However, the work involved in rewriting FSUIPC3 in this area to do the same is huge, and it simply isn't worthwhile at this stage. I have too much to do going forward. I am only applying easy changes to FSUIPC3 arising from ones first made to FSUIPC4, and that particular change is far from easy.

There should be a solution for your 6 axes, though. The interface program should be supplying those axes as the same 6 supported by the "joy" interface, not 5 from that set and one from the DirectInput set. That makes no sense.

It may well be as easy as a Registry change to do that -- but you will need to talk to the people who know your interface.

Regards

Pete