muchimi
commented
6 days ago In GremlinEx, which uses DirectInput, the axes are read in the sequence they appear in DirectInput, up to 8 axes. I've looked and it doesn't appear that the axis usage is read by DirectInput as it doesn't expose that information (I spend some time today looking at the API documentation and the C++ header). That data does exist at the USB descriptor level but not apparently in DirectInput, and GremlinEx does not read USB devices, it uses DirectX to do this, so we're limited by what DirectX provides, which is the count of devices. I'm going to look into this some more because there is an axis mapping structure returned, and I need to see if it skips an index which we can then use).
So when you say the axis name is wrong, you are completely correct in that the name is based on the sequence, and the "normal" sequence is X, Y Z, RX, RY, RZ, S1, S2 for the 8 axes. If you skip a sequence, GremlinEx won't be the wiser.
This said, I need to understand why it matters. Looks like you're using a winwing control panel - I don't have one of those so not sure how the mapping works but for now, use the sequence (number) of the axis rather than the name as the name is essentially arbitary and not used is any mapping, the index of the axis however is.
I'll do some more digging but yes, the name is based, for now, on no gaps in the sequence. It only looks for the first eight axes.
With v13.40.16m10 or earlier one of my vJoy axes were identified wrong: x,y,z and rx instead of x,y,rx and ry. Ry was assigned as y. The only workaround was to change the vJoy axe from ry to z (Image 1. For consistency I want to correct it (Image 2) because it's defined as those by the device (Image ICP). It's not recognized after the change (Image 3) and reboot. In the Settings the axes are shown correct (Image 4), but cant be choosen. Any idea to reread the axes information?