Jump to content

Question regarding number of DX buttons recognised by IL2 for single hardware device


Recommended Posts

Posted

I been flying IL2 since the start using my Thrustmaster Warthog joystick and throttle separately as standard DX devices. I decided to use the Thrustmaster TARGET scripting method again that combines the joystick and throttle in a single virtual device, which offers up to 128 DX buttons. This gives more flexibility as switches with two positions can now correctly assign two actions, not just in the 'on' position. I have also programmed my pinky switch as a modifier that simulates 'right control' on the keyboard, allowing me to double the button functionality using the S4 switch as a 'shift' button (workaround for IL2 not providing modifier buttons outside of keyboard buttons such as shift, alt & control). The big advantage of using this is that I can again use the slider axis on the throttle for zoom. I stopped using it as the slider had some noise, resulting in spikes in the zoom functionality that is very irritating on the eye. The TARGET software filters out noise in the combined virtual device, resulting in smooth axis performance.

 

So basically I started assigning buttons at DX1 on my Joystick, and ended up with something like DX72 (roughly as there are two gaps I left in) for the final buttons on the Throttle. With the Thrustmaster Combined device active, I noticed during the button assignment in IL2 that some of the throttle DX buttons (somewhere in the 60's) do not report the button presses correctly (it adds 'pov' behind the button names). After testing it appears that IL2 stops recognising these buttons, which is guess is at 64, which makes me think that IL2 perhaps has a hard limit of 64 DX buttons that it will recognise per hardware device.

 

Can anyone please confirm whether there is a hard cap on DX numbers per device? If any of the IL2 developers are reading this, would it be possible the raise the number of DX buttons recognised to 128 instead please, if that is the case?

 

I have attached my script file if anyone is interested. To use it in TARGET Script Editor (Not TARGET gui), just change the file extension from txt to tmc as usual.

 

My_IL2_Experiment.txt

Posted

Hello,

IL2 GB only 64 buttons per device. Above 64, you will have the _pov added and these buttons are ignored (or bad behaviour).

Have fun

Posted

There is already a topic for this with an answer from the devs:

 

 

Posted

Thank you very much for confirming and the link the other topic. I think it is clear that this is something that needs to be implemented at some point. Seeing that the latest update made some improvements to the keymapping section, one can only hope that time will be allocated to add at least 128 button support in the not too distant future.

Posted

We see more and more buttons over the years (including more complicated switches than are multiple buttons in one), but also innovative ideas like switching all buttons with a modifier. So then you can have twice as many virtual buttons as you have real buttons.

 

And we've seen companies playing with controller boxes that combine multiple real devices into one big device. I can see a future where all of this stuff is integrated. So you flip a switch on your throttle extension box, such as the bottom thing on the VKB throttle:

 

image.png.718b554f877518a80c79bdfb5c1688aa.png

 

And then it switches all the buttons on all your other devices too, like your joystick. And all of it requires only one cable going to your PC. If you have that, 128 buttons will probably become a problem real quick, but with the new Windows GameInput API, it should be possible.

But you need to keep in mind that they are working on a new game engine, so at best we'll get this in that new game engine, not in the current games all using the older engine.

Posted

I have been using Up/Middle/Down modifiers in conjunction with the pinky switch modifier on Thrustmaster gear since I got my first F22 Pro in 1998. That had the potential of 6 times the number of buttons simulated. But the software took care of this and that was before DX buttons became a thing.

 

While 1C is developing a new game, I am hoping that whatever they are building can be integrated as quality of life in the current IL2 GB product. I was surprised when I saw the changes to the control mapping functionality and it is very much welcomed and appreciated. However adding on and off states to buttons should really come with an expanded number of DX buttons past 64 to allow users to make us of this new capability in the control mapper. 

 

For the moment I will need to decide which extra states I can do without my profile and limit it to 64 for now. Once more buttons are recognised by IL2, I can just add those on top.

 

There are some very nice new products on the market. My Warthog is going on 13 years now and still going strong.

Posted

Hello,

One solution could be to create virtual controller for the stecs, but IL2 has problem with this (never succeed to have one). Other solution I used is to map button number greater than 64 is to assign a keyboard key to the buttons  (via configurator DevCfg).

 

Have fun

Posted
3 hours ago, KpaxBos said:

Hello,

One solution could be to create virtual controller for the stecs, but IL2 has problem with this (never succeed to have one). Other solution I used is to map button number greater than 64 is to assign a keyboard key to the buttons  (via configurator DevCfg).

 

Have fun

 

Thanks, yes, that will work as well. I am trying to minimise the number of manual assignments but you are right, that could work in the meantime.

  • 2 weeks later...
Posted
On 2/23/2024 at 2:23 AM, KpaxBos said:

via configurator DevCfg

I'm not aware of this. Can you post a link?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...