How many buttons does DCS recognise on a single device?

[jonsky7]

How many buttons does DCS recognise on a single device?

I'm having some issues.

I have a TM Warthog throttle, and I'm using the DX128 script that turns the switches from on-off to on-on. This was to avoid having to make bindings that were toggle switches, so to avoid having to actuate a switch twice to turn something on, and then off again.

So it now has more than 32 buttons which is what you see in windows usb game controller properties.

 

When I try to assign some keybinds, a modifier is automatically selected (LCtrl), and this has me confused. The keybinds that this gets added for then are troublesome. 

The AH-64D FCR Continuous and Single scan being one of the culprits. I can move the switch and nothing happens, but in my device viewer the switches are working flawlessly.

Any ideas anyone?

 

[MAXsenna]

21 minutes ago, jonsky7 said:

This was to avoid having to make bindings that were toggle switches, so to avoid having to actuate a switch twice to turn something on, and then off again.

I can't answer your question, while you do know you can use off states in DCS natively? 

[jonsky7]

I've actually just had another play with the scripting,

it is only when buttons 16,17,18 are pressed that the modifier is added. I changed it so the same switches pressed 51,52,53, and no modifier added.

But I will look into what you mentioned also. Thanks

[Hiob]

32 buttons isn‘t nowhere near of any critical threshold of buttons. Including logical buttons, I have something close to 150 buttons on my throttle.

It‘s more likely that the 3rd party script you‘re using causes problems (with DCS).

Edited September 11, 2024 by Hiob

[MAXsenna]

32 buttons isn‘t nowhere near of any critical threshold of buttons. Including logical buttons, I have something close to 150 buttons on my throttle.
It‘s more likely that the 3rd party script you‘re using causes problems (with DCS).

And you remember all those bindings in what way?

Sent from my SM-A536B using Tapatalk

[Hiob]

36 minutes ago, MAXsenna said:

And you remember all those bindings in what way?

Sent from my SM-A536B using Tapatalk
 

I don't use them all, but I know that all can be bound and are recognized by DCS without issues. That's what you get when you combine a Virpil throttle + button box.....

It's probably even more. I think the button box alone has ~ 100 physical buttons. Plus the virtual ones you can assign in the Virpil-Software and load on the devices. Never had any issue with DCS recognizing/binding any of them.

[AndyJWest]

As far as I'm aware, Windows limits a single device to 128 buttons. There are however ways to get around this by using multiple virtual 'devices'.

 

 

[MAXsenna]

I don't use them all, but I know that all can be bound and are recognized by DCS without issues. That's what you get when you combine a Virpil throttle + button box.....
It's probably even more. I think the button box alone has ~ 100 physical buttons. Plus the virtual ones you can assign in the Virpil-Software and load on the devices. Never had any issue with DCS recognizing/binding any of them.

Ah, I thought you were using all 150.
I try to map as close to the real thing as possible. Only way for me to remember.

Sent from my SM-A536B using Tapatalk

[Hiob]

28 minutes ago, MAXsenna said:

Ah, I thought you were using all 150.
I try to map as close to the real thing as possible. Only way for me to remember.

Sent from my SM-A536B using Tapatalk
 

I choose the generic Virpil stuff because when you use replica devices, they only ever fit one particular Aircraft anyway.
My strategy is to use the same basic bindings consistently throughout all Aircraft and use the mouse-clickable cockpit as much as possible.

Same problem, different coping mechanism.... 

[jonsky7]

Turns out I had a Voice Command action working off some button presses and I had forgot to make it module specific..... D'oh  

I spent hours trying to fix this lol.

[MAXsenna]

Turns out I had a Voice Command action working off some button presses and I had forgot to make it module specific..... D'oh  
I spent hours trying to fix this lol.

Do you use VAICOM?

Sent from my SM-A536B using Tapatalk

1 hour ago, Hiob said:

Same problem, different coping mechanism.... 

Absolutely!  

[jonsky7]

Just now, MAXsenna said:

Do you use VAICOM?

Sent from my SM-A536B using Tapatalk
 

No, tried it once, far too complicated for me, I just make my own profiles then I know what I have to say to get things to work.

[MAXsenna]

No, tried it once, far too complicated for me, I just make my own profiles then I know what I have to say to get things to work.

Oh, it gets easier fast! And you can change the phrases anyway. A nice feature though, is that I can have one single VoiceAttack profile for basically everything. If I say "gear up", it will trigger the relevant keypresses according to he module I'm in.

Sent from my SM-A536B using Tapatalk

[jonsky7]

On 9/11/2024 at 2:56 PM, MAXsenna said:

Oh, it gets easier fast! And you can change the phrases anyway. A nice feature though, is that I can have one single VoiceAttack profile for basically everything. If I say "gear up", it will trigger the relevant keypresses according to he module I'm in.

Sent from my SM-A536B using Tapatalk
 

Yeah, but I mostly use it for CTLD in multiplayer, I can just say "Bradley" and it will press the relevant buttons to give me a Bradley crate.

If I'm not mistaken, you still have to go through the menus saying "take 1", "take 3", "take 5" to do the same with Viacom?

[MAXsenna]

Yeah, but I mostly use it for CTLD in multiplayer, I can just say "Bradley" and it will press the relevant buttons to give me a Bradley crate.
If I'm not mistaken, you still have to go through the menus saying "take 1", "take 3", "take 5" to do the same with Viacom?

In VAICOM, you have commands directly for an un-edited radio "menu". VAICOM doesn't actually use the menu. For user made radio menu items, you can import them and then change the phrase to your liking.

Sent from my SM-A536B using Tapatalk

[_Hoss]

OAre you using Sedenion's Complete 128 dx hack SCRIPT?

I would only use it to get TEMPO presses out of buttons and momentary switches. And only if your set up is exclusively ThrustMaster. 

Example..... When I run DCS I have a WW Super Taurus, (Start Panel & Throttle w/handles, = 2 devices,  PTO2 = 1 device, K-51 Trim box = 1 (axis x 8 on my left). AVA & F/A-18 stick = 1, BlackHog A = 1, Master Arm Panel = 1, on the center mount. And Viper Panel on the right = 1, and the TPRs = 1 on the floor...... that works out to nine devices. I can use everything in DCS, but not IL2. I don't use TARGET or SimAppPro in DCS,  but only to update FW, and change physical / virtual button states on the WW and TM devices. (Virtual buttons on TM/VP, and axis to buttons and vice versa,, on WW stuff. I do run TARGET if and when I play IL2. It sees nine devices, so I merge the Stick, Viper Panel, and TPRs to "Combined" either in GUI or SCRIPT since IL2 doesn't care about 120 buttons anymore.

Like Gunny Highway said, we have to.... "improvise, Adapt, Overcome"........ 

"Always carry a knife with you, just in case there's cheesecake, or you need to stab someone in the throat" Gen. Mattis. 

Don't be afraid to experiment..... it's just ones and zeros..... 

In other words, don't be a myopic fanboi like I was to a particular mfg. 

 

My work in progress

Sitting behind me is a TMWH HOTAS, w/ MTSIM mounts, Crosswinds, and the TPS', and the M/A panel I still need to mount..

RSMapper, sees all my devices.

On Press commands - keyboard emulation, TEMPO

On Release commands - keyboard emulation

Chain Events / Sequences

Multiple game and aircraft profiles. 

KISS

 

Edited September 14, 2024 by _Hoss