Can I assign axis that don't exist in options?

[Archaic]

I switched from a Warthog to an X55 for functionality, and now I have knobs coming out the butt and pretty much have everything I *need* running properly, but there a few that would still be nice to add.

 

Can I add a radio volume axis to my RTY3/4 knobs? The option doesn't exist for the axis in keymapping. I haven't played around with the X55 software, thus far I'm just mapping in game since I really don't need multiple modes.

[Steph-JJ]

Look here

 

https://forums.eagle.ru/showthread.php?t=175260

 

perheps helpful to find another way

[Archaic]

Thanks but I didn't see anything there specifically addressing these rotary dials.

[funkyfranky]

No sure about the radio volumes but I added some axes for the lights. You have to add those lines to your input controller lua file, e.g. default.lua but maybe some other file for the X55.

 

axisCommands = {

...

{action = device_commands.Button_639, cockpit_device_id = devices.SYSLIGHTS, name = _('Dashboard U.V. Lights Knob'), category = _('Light Axes')},

{action = device_commands.Button_640, cockpit_device_id = devices.SYSLIGHTS, name = _('Dashboard Panel Lights Knob'), category = _('Light Axes')},

{action = device_commands.Button_641, cockpit_device_id = devices.SYSLIGHTS, name = _('Red Flood Lights Knob'), category = _('Light Axes')},

{action = device_commands.Button_642, cockpit_device_id = devices.SYSLIGHTS, name = _('Console Panel Lights Knob'), category = _('Light Axes')},

{action = device_commands.Button_644, cockpit_device_id = devices.SYSLIGHTS, name = _('White Flood Lights Knob'), category = _('Light Axes')},

{action = device_commands.Button_207, cockpit_device_id = devices.VTH_VTB, name = _('Auxiliary Gunsight Deflection'), category = _('HUD/VTB Axes')},

{action = device_commands.Button_209, cockpit_device_id = devices.VTH_VTB, name = _('Target Wingspan Knob'), category = _('HUD/VTB Axes')},

{action = device_commands.Button_192, cockpit_device_id = devices.VTH_VTB, name = _('Minimum Altitude Selector'), category = _('HUD/VTB Axes')},

{action = device_commands.Button_340, cockpit_device_id = devices.NAVINST, name = _('HSI Course Heading Selector'), category = _('HSI Axes')},

{action = device_commands.Button_488, cockpit_device_id = devices.RADAR, name = _('Radar Gain Dial'), category = _('Radar Axes')},

{action = device_commands.Button_610, cockpit_device_id = devices.RWR, name = _('Radar Gain Dial'), category = _('RWR Axes')},

{action = device_commands.Button_197, cockpit_device_id = devices.RWR, name = _('ECM Box LCD Display Brightness'), category = _('RWR Axes')},

...

}

 

If the radio volumes are in principle defined as axes you should be able to do a similar thing. Have a look at the clickabledata.lua file of the Mirage and figure out the necessary button numbers and cockpit device IDs.