Jump to content

axis controls for lights and volumes gone


Go to solution Solved by LeCuvier,

Recommended Posts

Posted

I guess a recent update 'streamlined' these control options. Presently, I can only assign buttons to increase and decrease these controls. Previously I had mapped axes to lights (aux,console,engine,flight,flood,form) and radio volumes (AIM seeker, ILS, TCN,FM,UHF,VHF)

How I can I restore these axis controls?

4930K @ 4.5, 32g ram, TitanPascal

Posted

In the clickabledata.lua file I did find this section for example


 

--Light System Control Panel

elements["PTR-LGHTCP-POSITION"]            = default_3_position_small_tumb(_("Position Lights, FLASH/OFF/STEADY"), devices.LIGHT_SYSTEM, device_commands.Button_8, 287)
elements["PTR-LGHTCP-FORMATION"]        = default_axis(_("Formation Lights"), devices.LIGHT_SYSTEM, device_commands.Button_9, 288, nil, nil, nil, nil, nil, {70, -135},{90,-45})
elements["PTR-LGHTCP-ANTICOLLISION"]    = electrically_held_switch(_("Anticollision Lights"), devices.LIGHT_SYSTEM, device_commands.Button_10, device_commands.Button_11, 289)
elements["PTR-LGHTCP-ENG-INST"]            = default_axis(_("Engine Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_1, 290, nil, nil, nil, nil, nil, {70, -135},{90,-45})
elements["PTR-LGHTCP-NOSE-ILLUM"]        = default_2_position_small_tumb(_("Nose Illumination"), devices.LIGHT_SYSTEM, device_commands.Button_12, 291)
elements["PTR-LGHTCP-FLIGHT-INST"]        = default_axis(_("Flight Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_2, 292, nil, nil, nil, nil, nil, {70, -135},{180,-45})
elements["PTR-LGHTCP-AUX-INST"]            = default_axis(_("Auxiliary Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_3, 293, nil, nil, nil, nil, nil, {70, -135},{140,-45})
elements["PTR-LGHTCP-SIGNAL-LTS"]        = default_2_position_small_tumb(_("Signal Lights"), devices.LIGHT_SYSTEM, device_commands.Button_13, 294)
elements["PTR-LGHTCP-ACCEL-COMP"]        = default_2_position_small_tumb(_("Accelerometer & Compass Lights"), devices.LIGHT_SYSTEM,device_commands.Button_4, 295)
elements["PTR-LGHTCP-FLOOD"]            = default_axis(_("Flood Light"), devices.LIGHT_SYSTEM, device_commands.Button_5, 296, nil, nil, nil, nil, nil, {70, -135},{180,-55})
elements["PTR-LGHTCP-CONSOLE"]            = default_axis(_("Console Light"), devices.LIGHT_SYSTEM, device_commands.Button_6, 297, nil, nil, nil, nil, nil, {70, -135},{180,-45})
elements["PTR-LIGHTS-LAND"]                = default_3_position_tumb(_("Land Taxi Lights"), devices.LIGHT_SYSTEM, device_commands.Button_14, 655, false, false, {-0.1,0.1}, {{0,0.2},{0,0.2}}, 2)
elements["PTR-ALCP-RSIL"]                = default_axis(_("Refuel Status Indexer Lights"), devices.LIGHT_SYSTEM, device_commands.Button_15, 193, 0.0, nil, nil, nil, nil, {80, -45})
elements["PTR-ALCP-WPNSTA"]                = default_axis(_("Weapon Station Lights. No function"), devices.LIGHT_SYSTEM, device_commands.Button_16, 195, 0.0, nil, nil, nil, nil, {90, -45}) -- No function in A-10C
elements["PTR-ALCP-NVIS-LTS"]            = default_3_position_tumb(_("Nightvision Lights"), devices.LIGHT_SYSTEM, device_commands.Button_17, 194, false, false, {-0.1,0.1}, {{0,0.2},{0,0.2}}, 2)
elements["PTR-FSCP-RCVR-LT"]            = default_axis(_("Refueling Lighting Dial")     ,devices.LIGHT_SYSTEM, device_commands.Button_18, 116, 0.0, nil, nil, nil, nil, {90, -45})
elements["PTR-ALCP-HARSSAS"]            = default_2_position_tumb(_("HARS-SAS Override/NORM"), devices.AUTOPILOT,device_commands.Button_31, 196)
elements["PTR-ALCP-FDBAL-TEST"]         = default_button(_("Fire Detect Bleed Air Test"), devices.SYS_CONTROLLER, device_commands.Button_4, 198,1, {0,1})

It clearly indicates that the lighting controls have axes but they are not showing up in the new LARGE controls setting screen.

 

Help?

4930K @ 4.5, 32g ram, TitanPascal

  • Solution
Posted

It's funny; I had added a bunch of axis comands before ED had added them. Fortunately, I didn't delete my additions. Here they are:

{action = 3001, cockpit_device_id = 49, name = _('Engine Instruments Lights Axis')},
{action = 3002, cockpit_device_id = 49, name = _('Flight Instruments Lights Axis')},
{action = 3003, cockpit_device_id = 49, name = _('Auxiliary Instruments Lights Axis')},
{action = 3005, cockpit_device_id = 49, name = _('Flood Light Axis')},
{action = 3006, cockpit_device_id = 49, name = _('Console Light Axis')},
{action = 3011, cockpit_device_id = 54, name = _('UHF Radio Volume Axis')},
{action = 3005, cockpit_device_id = 55, name = _('VHF AM Radio Volume Axis')},
{action = 3005, cockpit_device_id = 56, name = _('VHF FM Radio Volume Axis')},
{action = 3013, cockpit_device_id = 38, name = _('Yaw Trim Knob Axis')},

I think these will still work.
You probably know: the "action" number is = Button_No + 3000.
The device ID for "LIGHT_SYSTEM" = 49 is good for most of your items. You find other device ID numbers in "devices.lua".

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...