Logitech X56 Map of what ED calls the buttons

Hawkcode

H
Hi, I was looking for a Map of the X56 HOTAS that shows the button numbers that ED shows when editing the Controller bindings.

Like the Fire Button is <1>.

Anybody know where I can find one? It would help when looking at an option to Deploy Landing gear and it says Joy 23 or something like that.

Thanks!
 

Hawkcode

H
I'm not looking for What My bindings are, I'm looking for what ED calls each Button, Joystick. So the fire button would show <1> , The Top Left hat on the stick would show Up is 10. down id 11, left is 12 etc.

I know how to use EDRefCard.
 

Hawkcode

H
BTW would you know if the 3 position switch on the Throttle works with ED? So you can have multiple settings based on whether it is in Pos 1, 2 or 3?
 

VerticalBlank

VerticalBlank

metatheurgist

metatheurgist
Hawkcode said:
I'm not looking for What My bindings are, I'm looking for what ED calls each Button, Joystick. So the fire button would show <1> , The Top Left hat on the stick would show Up is 10. down id 11, left is 12 etc.
Click to expand...
Open up your controller properties. It's whatever they are called in Windows.
 

robbyp

robbyp
Use my program https://github.com/EDDiscovery/MultiJoyStickTest/releases/tag/Release_1_1_0 which shows you all your controllers on one screen, and will indicate the windows button number to you as you press the joystick button.

I use this before starting a play session to make sure the controllers are all there and correct (so Elite does not lose the bindings). Its also good for MSFS to make sure your complicated controller setup is ready for action.
 

Rat Catcher

Rat Catcher
robbyp said:
Use my program https://github.com/EDDiscovery/MultiJoyStickTest/releases/tag/Release_1_1_0 which shows you all your controllers on one screen, and will indicate the windows button number to you as you press the joystick button.

I use this before starting a play session to make sure the controllers are all there and correct (so Elite does not lose the bindings). Its also good for MSFS to make sure your complicated controller setup is ready for action.
Click to expand...
Nice.... Sadly, using Virpil kit with the throttle split into 3 devices, it only shows the first block. We really need Frontier to remove the 32 button limit!
 

robbyp

robbyp
So multijoysticktester just uses the standard DirectX DirectInput calls to find devices and get button states. The project enumerate all the devices returned from direct X. The button count is read directly from direct x and is not limited to 32.

So i'm not sure that the Virpil kit is doing - maybe creating 'fake' new devices with buttons?

This is the problem Frontier has with doing this. Its not simple, and full of risk. The whole supporting controllers in windows is a balancing act which you can fall off of very easily.
 

Rat Catcher

Rat Catcher
robbyp said:
So i'm not sure that the Virpil kit is doing - maybe creating 'fake' new devices with buttons?
Click to expand...
It inserts 3 controllers, thus:
hotas.png


I've not checked what DirectX DirectInput displays yet.

It wasn't a criticism of the software - only of the 32 button limit (which affects the X series also, they, like your software, grab the 1st bank from the split) which entails the split in the first place.

The problem with the split is that, in ED (& DCS) you can have 4 'button 1' etc. in the controls list, each referring to a different button.
 

robbyp

robbyp
I know you were not. This is what I thought it would do - set up new 'fake' devices for the other buttons.

I wonder why Multijoysticktester does not see them - it must be excepting during creation due to something about those other devices. Without a virpil, or a willing helper, I can't fix that ;-)
 

metatheurgist

metatheurgist
I remember dreaming about having a 2 button stick for Elite 84 and that the second button would actually have a different function other than also being fire. Now we complain that 32 buttons isn't enough. Times change! 😄
 

Rat Catcher

Rat Catcher
robbyp said:
I know you were not. This is what I thought it would do - set up new 'fake' devices for the other buttons.

I wonder why Multijoysticktester does not see them - it must be excepting during creation due to something about those other devices.
Click to expand...
It is strange.
robbyp said:
Without a virpil, or a willing helper, I can't fix that ;-)
Click to expand...
I'd be happy to help - provided it is something within my ability!
 
You must log in or register to reply here.
Back
Top Bottom