skypickle Posted January 12, 2023 Posted January 12, 2023 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? 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. 4930K @ 4.5, 32g ram, TitanPascal
Solution jaylw314 Posted January 13, 2023 Solution Posted January 13, 2023 Quick search does wonders:
skypickle Posted January 14, 2023 Author Posted January 14, 2023 (edited) Thank you. That topic was actually started by me but I was never notiified of a reply. I also just saw it in the routine of checking my old threads. Edited January 14, 2023 by skypickle 4930K @ 4.5, 32g ram, TitanPascal
Recommended Posts