ALQ-165 ECM bindings for Winwing Combat Panel (or any USB device)

[RSharpe]

I have a Winwing Combat Panel that I want to bind the ECM knob to it.

 

However. I have found that all bindings for the ALQ-165 are blacked-out and unbindable to the Combat Panel, and ALL USB devices except the keyboard. It's one of the only things I've not been able to bind. Every other switch, button, knob and axis slider for the panels has been bindable.

 

Does anyone have any clue why it's like this and how to fix it?

 

Screenshot of bindings attached. All USB devices have been blacked-out.

[LeCuvier]

The ALQ-165 commands can be bound to all of my game controllers. I have bound the CCW/CW commands to my DSD button box and they work fine.

These commands are defined in the file "default.lua" in the folder "...\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick", and they are available for all game controllers. The lines of code below define these commands.

 

-- AN/ALQ-165 Airborne Self-Protection Jammer (ASPJ)
{    down = ASPJ_commands.ASPJ_SwitchChange_ITER,                    cockpit_device_id = devices.ASPJ,    value_down = -1.0,                        name = _('ALQ-165 ECM Mode Switch - CCW'),                    category = {_('Instrument Panel'), _('ALQ-165')}},
{    down = ASPJ_commands.ASPJ_SwitchChange_ITER,                    cockpit_device_id = devices.ASPJ,    value_down =  1.0,                        name = _('ALQ-165 ECM Mode Switch - CW'),                    category = {_('Instrument Panel'), _('ALQ-165')}},
{    down = ASPJ_commands.ASPJ_SwitchChange,                            cockpit_device_id = devices.ASPJ,    value_down =  0.4,                        name = _('ALQ-165 ECM Mode Switch - XMIT'),                    category = {_('Instrument Panel'), _('ALQ-165')}},
{    down = ASPJ_commands.ASPJ_SwitchChange,                            cockpit_device_id = devices.ASPJ,    value_down =  0.3,                        name = _('ALQ-165 ECM Mode Switch - REC'),                    category = {_('Instrument Panel'), _('ALQ-165')}},
{    down = ASPJ_commands.ASPJ_SwitchChange,                            cockpit_device_id = devices.ASPJ,    value_down =  0.2,                        name = _('ALQ-165 ECM Mode Switch - BIT'),                    category = {_('Instrument Panel'), _('ALQ-165')}},
{    down = ASPJ_commands.ASPJ_SwitchChange,                            cockpit_device_id = devices.ASPJ,    value_down =  0.1,                        name = _('ALQ-165 ECM Mode Switch - STBY'),                    category = {_('Instrument Panel'), _('ALQ-165')}},
{    down = ASPJ_commands.ASPJ_SwitchChange,                            cockpit_device_id = devices.ASPJ,    value_down =  0.0,                        name = _('ALQ-165 ECM Mode Switch - OFF'),                    category = {_('Instrument Panel'), _('ALQ-165')}},

Are any or all of the other F/A-18C commands available for binding?

Edit: I just saw a review of the combat panel. The reviewer said that the command bindings for the ALQ-165 were not yet available at the time of his review.

They certainly are available in the Open Beta. But I found that they are not (yet) available in the stable release. So, this is not a bug. The problem is that you are using the stable release. If you want all functionality that's available today, I suggest you install the Open Beta.

Edited March 8, 2021 by LeCuvier

[markturner1960]

you can use this change to the .lua scripts, its not my work, I cant remember the guys name off hand, but the original post is in the winwing forum....

 

you have to install again each update though

Mods (1).zip

[Bunny Clark]

On 3/8/2021 at 10:44 AM, LeCuvier said:

The problem is that you are using the stable release.

This isn't true any more. As far as I know, Stable and Open Beta are the same build right now, and the ALQ-165 controls are bindable for me in Stable. 

 

Something must have gotten borked with your controls file in the update, which is not an unusual thing to happen.

[LeCuvier]

True, the stable version now includes these commands. Maybe RSharpe had not updated. But since he has not come back with comments it's useless to speculate.

People have spent time to try and figure out what his problem is, and it would be good style to come back and state where he is with this.

[Fusedspine33]

I use OVGME for my monitor configuration with Helios. I had the same issue and found that the joystick default.lua was being overwritten causing the new binds to be not assignable. I cut and pasted the new commands into the OVGME file and they now work.


Sent from my iPad using Tapatalk

[RSharpe]

DCS recently wiped out my bindings for everything, and I just ended up deleting my user folder and started rebinding everything from scratch. It's working now