DirectInput supports 128 buttons. At least that's my understanding.
Last edited:
Request for more than 32 buttons (Virpil throttle)
Is it possible to estimate the effort to fix this issue? What would be required?
Classic necro.
So i googled nasa, and came up with a 404
The cosmic object you are looking for has disappeared beyond the event horizon.
True story!
Yes. At least 139 buttons is my best guess currently, but i confess to being a little hazy on the finer points of OP's. angst.
So i googled nasa, and came up with a 404
The cosmic object you are looking for has disappeared beyond the event horizon.
True story!
Shameless but justified
![[VR] Captain_Obvious](https://forums-cdn.zaonce.net/data/avatars/m/176/176192.jpg?1620829029){kind=avatar}
True. I'm still working with an older firmware for my Virpil gear that allows device splitting. And that exclusively for this game. Would be great to have this issue solved.
At least the issue has been confirmed by FD. Hope we will see a "solved" tag soon in the issue tracker
yeah that would be great
How often can we BUMP a thread?
Still waiting for good news
Still waiting for good news
Often as we like bump. We should maybe limit it once a day. It's in their tracker as confirmed, we are all just unsure if they intend to do anything about it.
I have spent some time doing some research on where this limit originates and it seems like this could all have been an accident, to limit the input to 32 buttons...
You see, when you use DirectInput, there are two data structures DIJOYSTATE and DIJOYSTATE2. These two are similar, with two differences.
DIJOYSTATE only has support for upto 32 buttons and no extra analogue data
DIJOYSTATE2 have support for upto 128 buttons and some extra analogue data, like how fast you changed the input, ie are you moving your stick slow or fast, etc. useful for stuff like ForceFeedback..
So when was DIJOYSTATE2 added to DirectX? it came in DirectX 8.0 which was released late 2001 Now consider that the first version in Kickstarter arrived late 2013...
Now this is just one way to interact with joysticks in DirectX... and there plenty more options, but it should give an idea on how this could have been avoided, as there had been support for 128 buttons in DirectX for over a decade when the Kickstarter started...
You see, when you use DirectInput, there are two data structures DIJOYSTATE and DIJOYSTATE2. These two are similar, with two differences.
DIJOYSTATE only has support for upto 32 buttons and no extra analogue data
DIJOYSTATE2 have support for upto 128 buttons and some extra analogue data, like how fast you changed the input, ie are you moving your stick slow or fast, etc. useful for stuff like ForceFeedback..
So when was DIJOYSTATE2 added to DirectX? it came in DirectX 8.0 which was released late 2001 Now consider that the first version in Kickstarter arrived late 2013...
Now this is just one way to interact with joysticks in DirectX... and there plenty more options, but it should give an idea on how this could have been avoided, as there had been support for 128 buttons in DirectX for over a decade when the Kickstarter started...
That is very good info.
As someone who has no experiance with programming, I ask myself how difficult it would be to fix that?
And please dont tell me you only have to add a "2" to the data structure link
As someone who has no experiance with programming, I ask myself how difficult it would be to fix that?
And please dont tell me you only have to add a "2" to the data structure link
If they use this method, for reading joystick input, then in a very simplistic form, that could be all that is needed, but reality is often more complicated...so there always appear to be some part of the code that would reject this and simply refuse to work, without a considerably amount of work, so most stuff could work, and then something stupid like get into the menu would stop working if bound to a button 33+That is very good info.
As someone who has no experiance with programming, I ask myself how difficult it would be to fix that?
And please dont tell me you only have to add a "2" to the data structure link
Then lets hope one dev will try it out and we all will have luck.
Sure, is more than optimistic, but who knows, we all deserve to be a bit lucky
Sure, is more than optimistic, but who knows, we all deserve to be a bit lucky
Last edited:
Returning to give this ol' thread another bump. I'm glad I've been able to use an outdated version of the Virpil firmware to (so far) keep my throttle working correctly. But every now and then, Elite seems to get confused and shifts controls to the wrong buttons. Seems like the Odyssey Alpha could've been the culprit.
Glad to hear that they're maybe acknowledging this as a bug. Let's hope it continues to move.
Glad to hear that they're maybe acknowledging this as a bug. Let's hope it continues to move.
interesting, was also thinking of bringing this thread back to page one but hold back.
I still dream that it will be in the patchnotes of Odyssey release, although I am certain it wont happen.
I still dream that it will be in the patchnotes of Odyssey release, although I am certain it wont happen.
Pretty sure that is a dream, but what is life without hope eh?
Checked in to see if my hopes came true that this was fixed as a part of the Odyssey Alpha. Sad to hear it hasn't been. Its a huge pain having to rely on third party software just to play the game with my throttle. Fingers crossed that this will be fixed in the full release...