First sanity check is the first time I've heard of that bug. I can replicate it but it doesn't seem to be related to the issue.
When I played the demo I was lucky enough to have the stick itself picked up as the first detected controller. I might have gotten the first eight buttons thing slightly wrong (the weapon release button on the stick is button 20 but it was bound just fine) but not all buttons bind correctly or at all, which is the issue regarding the buttons. The buttons I noticed did not bind correctly are the hats. Some of the hat switches do bind, bind as "None-" (or some other weird name) or do not bind at all. Some other non-hat buttons, i.e. the pinky switch, also exhibit the same or similar behaviour. I haven't been able to bind any throttle or rudder pedal inputs.
My controllers are all separate devices. If you're asking about a screenshot of my devices in joy.cpl:
View attachment 12773
Devices show up in dxdiag as follows:
Device Name Vendor ID Product ID WINWING JOYSTICK BASE2 + JGRIP-F16 0x4098 0xBE48 WINWING THROTTLE BASE2 + TGRIP-F16 0x4098 0xBE37 MFG Crosswind V2 0x16D0 0x0A38
Thanks, that gives me a lot to work with. I can guess what the issue is with most of them is, the interface was originally built around gamepads and will need expanding for your stick.
Why only one joystick is getting recognised is something of a mystery.
If you could hit the properties button and show the page it opens it’ll let me know what axes are used by your devices.