Panthir Posted December 27, 2017 Share Posted December 27, 2017 Guys, any solution for the ECM knob? At least for the positions RCV and ECM. My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27" My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE. My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic. Link to comment Share on other sites More sharing options...
Deezle Posted December 27, 2017 Share Posted December 27, 2017 Deezle- I've been searching around a lot, but couldn't find the answer to this. Where did you get the "3289" command from? Thanks! I use the clickabledata.lua to get the commands. Guys, any solution for the ECM knob? At least for the positions RCV and ECM. How do you wish to control it? If you're using a single toggle switch, this will set it to RPT when the switch is on and RCV when your switch is off. {down = 3275, up = 3275, cockpit_device_id = 29, value_down = 1, value_up = .75, name = _('Jammer RPT/RCV'), category = _('ECM')},And if you want a command for each position you can use this. {down = 3275, cockpit_device_id = 29, value_down = 1, name = _('Jammer RPT'), category = _('ECM')}, {down = 3275, cockpit_device_id = 29, value_down = .75, name = _('Jammer RCV'), category = _('ECM')}, Intel 9600K@4.9GHz, Asus Z390, 32GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe 34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5 My Pit Build, VKB Gunfighter Pro w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals, Cougar MFDs, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer Link to comment Share on other sites More sharing options...
Panthir Posted December 28, 2017 Share Posted December 28, 2017 Many many thanks mate! My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27" My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE. My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic. Link to comment Share on other sites More sharing options...
Chain Posted December 29, 2017 Share Posted December 29, 2017 Any chance we could get bindable UFC BRT, VOL knobs, COMM 1 and COMM 2 pull switches and rotary actions for the COMM 1 and COMM 2 switches? Would be nice to have axis control for volume knobs. I'd like to bind these to my "button box" :) Thanks! System: Windows 10 | i7-7700K @ 4.5 Ghz | 32GB of RAM | Nvidia GTX 1080, 3440x1440 | DELL Ultrawide U3415W | Samsung 960 Evo M.2 and 2 TB Seagate Barracuda | TM Warthog Hotas | SLAW F-16 Pedals | Oculus Rift CV1 and HTC Vive PRO VR + High fidelity F/A-18C simpit :) Link to comment Share on other sites More sharing options...
Deezle Posted December 29, 2017 Share Posted December 29, 2017 Any chance we could get bindable UFC BRT, VOL knobs, COMM 1 and COMM 2 pull switches and rotary actions for the COMM 1 and COMM 2 switches? Would be nice to have axis control for volume knobs. I'd like to bind these to my "button box" :) Thanks! Axis binds are pretty simple. Here's a few. --Lighting {action = 3510, cockpit_device_id = 32, name = _('Formation Lights')}, {action = 3636, cockpit_device_id = 33, name = _('Console Lights')}, {action = 3635, cockpit_device_id = 33, name = _('Instrument Lights')}, {action = 3637, cockpit_device_id = 33, name = _('Flood Lights')}, {action = 3272, cockpit_device_id = 20, name = _('EDP Brightness Control')}, {action = 3289, cockpit_device_id = 22, name = _('HUD Off/Brightness Control')}, {action = 3295, cockpit_device_id = 23, name = _('Display Brightness Control')}, {action = 3194, cockpit_device_id = 25, name = _('MPCD Left Off/Brightness Control')}, {action = 3195, cockpit_device_id = 26, name = _('MPCD Right Off/Brightness Control')}, --Volume {action = 3298, cockpit_device_id = 23, name = _('Comm 1 Volume Control')}, {action = 3299, cockpit_device_id = 23, name = _('Comm 2 Volume Control')}, {action = 3614, cockpit_device_id = 7, name = _('V/UHF RSC Volume Knob')}, {action = 3629, cockpit_device_id = 4, name = _('ICS Aux Volume Knob')}, {action = 3630, cockpit_device_id = 4, name = _('ICS Ground Volume Knob')}, Intel 9600K@4.9GHz, Asus Z390, 32GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe 34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5 My Pit Build, VKB Gunfighter Pro w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals, Cougar MFDs, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer Link to comment Share on other sites More sharing options...
funkyfranky Posted December 29, 2017 Share Posted December 29, 2017 Axis binds are pretty simple. However, most of them only start working after half of the dial has been turned. So it's best to add a user defined curve like this My list {action = int_light_commands.Knob_Instr_Lights, cockpit_device_id = devices.LTINT, name = _('FF Instruments Lights')}, {action = int_light_commands.Knob_Console_Lights, cockpit_device_id = devices.LTINT, name = _('FF Console Lights')}, {action = int_light_commands.Knob_Flood_Lights, cockpit_device_id = devices.LTINT, name = _('FF Flood Lights')}, {action = int_light_commands.Knob_Annunciator_Lights, cockpit_device_id = devices.LTINT, name = _('FF Annunciator Lights')}, {action = int_light_commands.Flood_Right_Canopy_Frame_Top, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Right Top')}, {action = int_light_commands.Flood_Right_Canopy_Frame_Btm, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Right Bottom')}, {action = int_light_commands.Flood_Right_BH_FWD, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Right Forward')}, {action = int_light_commands.Flood_Right_BH_AFT_Front, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Right Aft Front')}, {action = int_light_commands.Flood_Right_BH_AFT_Back, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Right Aft Back')}, {action = int_light_commands.Flood_Left_BH_AFT_Back, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Left Aft Back')}, {action = int_light_commands.Flood_Left_BH_AFT_Front, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Left Aft Front')}, {action = int_light_commands.Flood_Left_BH_FWD, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Left Forward')}, {action = int_light_commands.Flood_Left_Canopy_Frame_Btm, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Left Bottom')}, {action = int_light_commands.Flood_Left_Canopy_Frame_Top, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Left Top')}, {action = edp_commands.BRT_Knob, cockpit_device_id = devices.EDP, name = _('FF EDP Brightness Control')}, {action = hud_commands.DisplayBRTKnob, cockpit_device_id = devices.HUDCONTROL, name = _('FF HUD Off/Brightness Control')}, {action = hud_commands.VideoBRTKnob, cockpit_device_id = devices.HUDCONTROL, name = _('FF HUD Video Brightness Control')}, {action = hud_commands.VideoCONTKnob, cockpit_device_id = devices.HUDCONTROL, name = _('FF HUD Video Contrast Control')}, {action = ufc_commands.Knob_BRT, cockpit_device_id = devices.UFCCONTROL, name = _('FF Display Brightness Control')}, {action = ufc_commands.Knob_Comm1_Vol, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 1 Volume Control')}, {action = ufc_commands.Knob_Comm2_Vol, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 2 Volume Control')}, {action = ufc_commands.Knob_Comm1_Chnl, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 1 Channel Selector'), category = _('_My Buttons')}, {action = ufc_commands.Knob_Comm2_Chnl, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 2 Channel Selector'), category = _('_My Buttons')}, {action = fqi_commands.BingoSet, cockpit_device_id = devices.FQIS, name = _('FF Bingo Fuel Set Knob')}, {action = mpcd_l_commands.Knob_OFF_BRT, cockpit_device_id = devices.MPCD_LEFT, name = _('FF MPCD Left Off/Brightness Control')}, {action = mpcd_r_commands.Knob_OFF_BRT, cockpit_device_id = devices.MPCD_RIGHT, name = _('FF MPCD Right Off/Brightness Control')}, {action = inst_commands.Knob_Altimeter, cockpit_device_id = devices.ADC, name = _('FF Barometric Pressure Calibration')}, {action = fcs_commands.Knob_FRICTION_LEFT, cockpit_device_id = devices.FLIGHTCONTROLS, name = _('FF Throttle Lever Friction Knob')}, {action = fcs_commands.Knob_FRICTION_RIGHT, cockpit_device_id = devices.FLIGHTCONTROLS, name = _('FF Nozzle Lever Friction Knob')}, {action = engine_commands.Handle_NOZZLE_CONTROL, cockpit_device_id = devices.VREST, name = _('FF Nozzle Control Lever')}, {action = engine_commands.Handle_NOZZLE_STO_STOP, cockpit_device_id = devices.VREST, name = _('FF STO Stop Lever')}, {action = ext_light_commands.Knob_FORM_LT, cockpit_device_id = devices.LTEXT, name = _('FF Formation Lights Knob')}, {action = radio_commands.Knob_VOLUME, cockpit_device_id = devices.RSC, name = _('FF V/UHF RSC Volume Knob')}, {action = radio_commands.Knob_CHAN_FREQ, cockpit_device_id = devices.RSC, name = _('FF V/UHF RSC Chan/Freq Knob')}, {action = acnip_commands.Knob_AUX_VOL, cockpit_device_id = devices.INTERCOM, name = _('FF ICS Aux Volume Knob')}, {action = acnip_commands.Knob_GND_VOL, cockpit_device_id = devices.INTERCOM, name = _('FF ICS Ground Volume Knob')}, A warrior's mission is to foster the success of others. i9-12900K | MSI RTX 3080Ti Suprim X | 128 GB Ram 3200 MHz DDR-4 | MSI MPG Edge Z690 | Samung EVO 980 Pro SSD | Virpil Stick, Throttle and Collective | MFG Crosswind | HP Reverb G2 RAT - On the Range - Rescue Helo - Recovery Tanker - Warehouse - Airboss Link to comment Share on other sites More sharing options...
NTolerance Posted December 29, 2017 Share Posted December 29, 2017 Would a Station 2 Pushbutton <-> Station 3 Pushbutton toggle make any sense for switching between A2G weapons? I heard somewhere that this aircraft only supports two A2G weapons loaded at one time, and since stations 1-7 are generally for Sidewinders which have their own dedicated bind, a toggle between stations 2-6 and 3-5 could possibly make attack runs with multiple weapons easier. I'm currently using the china hat on my TM Warthog to switch between these stations, but it would be cool to get it down to a single button, and then the china hat could be used for something else. Link to comment Share on other sites More sharing options...
Chain Posted December 30, 2017 Share Posted December 30, 2017 (edited) Thanks! This helped a lot :thumbup: One mystery remains. I can't figure out how to create a bind for the COMM1 and COMM2 channel selector pull/push option. However, most of them only start working after half of the dial has been turned. So it's best to add a user defined curve like this My list {action = int_light_commands.Knob_Instr_Lights, cockpit_device_id = devices.LTINT, name = _('FF Instruments Lights')}, {action = int_light_commands.Knob_Console_Lights, cockpit_device_id = devices.LTINT, name = _('FF Console Lights')}, {action = int_light_commands.Knob_Flood_Lights, cockpit_device_id = devices.LTINT, name = _('FF Flood Lights')}, {action = int_light_commands.Knob_Annunciator_Lights, cockpit_device_id = devices.LTINT, name = _('FF Annunciator Lights')}, {action = int_light_commands.Flood_Right_Canopy_Frame_Top, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Right Top')}, {action = int_light_commands.Flood_Right_Canopy_Frame_Btm, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Right Bottom')}, {action = int_light_commands.Flood_Right_BH_FWD, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Right Forward')}, {action = int_light_commands.Flood_Right_BH_AFT_Front, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Right Aft Front')}, {action = int_light_commands.Flood_Right_BH_AFT_Back, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Right Aft Back')}, {action = int_light_commands.Flood_Left_BH_AFT_Back, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Left Aft Back')}, {action = int_light_commands.Flood_Left_BH_AFT_Front, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Left Aft Front')}, {action = int_light_commands.Flood_Left_BH_FWD, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Left Forward')}, {action = int_light_commands.Flood_Left_Canopy_Frame_Btm, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Left Bottom')}, {action = int_light_commands.Flood_Left_Canopy_Frame_Top, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Left Top')}, {action = edp_commands.BRT_Knob, cockpit_device_id = devices.EDP, name = _('FF EDP Brightness Control')}, {action = hud_commands.DisplayBRTKnob, cockpit_device_id = devices.HUDCONTROL, name = _('FF HUD Off/Brightness Control')}, {action = hud_commands.VideoBRTKnob, cockpit_device_id = devices.HUDCONTROL, name = _('FF HUD Video Brightness Control')}, {action = hud_commands.VideoCONTKnob, cockpit_device_id = devices.HUDCONTROL, name = _('FF HUD Video Contrast Control')}, {action = ufc_commands.Knob_BRT, cockpit_device_id = devices.UFCCONTROL, name = _('FF Display Brightness Control')}, {action = ufc_commands.Knob_Comm1_Vol, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 1 Volume Control')}, {action = ufc_commands.Knob_Comm2_Vol, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 2 Volume Control')}, {action = ufc_commands.Knob_Comm1_Chnl, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 1 Channel Selector'), category = _('_My Buttons')}, {action = ufc_commands.Knob_Comm2_Chnl, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 2 Channel Selector'), category = _('_My Buttons')}, {action = fqi_commands.BingoSet, cockpit_device_id = devices.FQIS, name = _('FF Bingo Fuel Set Knob')}, {action = mpcd_l_commands.Knob_OFF_BRT, cockpit_device_id = devices.MPCD_LEFT, name = _('FF MPCD Left Off/Brightness Control')}, {action = mpcd_r_commands.Knob_OFF_BRT, cockpit_device_id = devices.MPCD_RIGHT, name = _('FF MPCD Right Off/Brightness Control')}, {action = inst_commands.Knob_Altimeter, cockpit_device_id = devices.ADC, name = _('FF Barometric Pressure Calibration')}, {action = fcs_commands.Knob_FRICTION_LEFT, cockpit_device_id = devices.FLIGHTCONTROLS, name = _('FF Throttle Lever Friction Knob')}, {action = fcs_commands.Knob_FRICTION_RIGHT, cockpit_device_id = devices.FLIGHTCONTROLS, name = _('FF Nozzle Lever Friction Knob')}, {action = engine_commands.Handle_NOZZLE_CONTROL, cockpit_device_id = devices.VREST, name = _('FF Nozzle Control Lever')}, {action = engine_commands.Handle_NOZZLE_STO_STOP, cockpit_device_id = devices.VREST, name = _('FF STO Stop Lever')}, {action = ext_light_commands.Knob_FORM_LT, cockpit_device_id = devices.LTEXT, name = _('FF Formation Lights Knob')}, {action = radio_commands.Knob_VOLUME, cockpit_device_id = devices.RSC, name = _('FF V/UHF RSC Volume Knob')}, {action = radio_commands.Knob_CHAN_FREQ, cockpit_device_id = devices.RSC, name = _('FF V/UHF RSC Chan/Freq Knob')}, {action = acnip_commands.Knob_AUX_VOL, cockpit_device_id = devices.INTERCOM, name = _('FF ICS Aux Volume Knob')}, {action = acnip_commands.Knob_GND_VOL, cockpit_device_id = devices.INTERCOM, name = _('FF ICS Ground Volume Knob')}, Edited December 30, 2017 by Chain System: Windows 10 | i7-7700K @ 4.5 Ghz | 32GB of RAM | Nvidia GTX 1080, 3440x1440 | DELL Ultrawide U3415W | Samsung 960 Evo M.2 and 2 TB Seagate Barracuda | TM Warthog Hotas | SLAW F-16 Pedals | Oculus Rift CV1 and HTC Vive PRO VR + High fidelity F/A-18C simpit :) Link to comment Share on other sites More sharing options...
hansangb Posted December 30, 2017 Share Posted December 30, 2017 How are you guys coming up with this code? Nero.ger, Your code works, Thanks If you have a little background in programming, it helps But it's certainly note required. If you read +/- 15 posts or so from this post, you should start to understand what the lua codes are doing hsb HW Spec in Spoiler --- i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1 Link to comment Share on other sites More sharing options...
EinsteinEP Posted December 30, 2017 Share Posted December 30, 2017 I can't figure out how to create a bind for the COMM1 and COMM2 channel selector pull/push option. {down = ufc_commands.Button_Comm1, up = ufc_commands.Button_Comm1, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm1 Button'), category = _('Up Front Control')}, {down = ufc_commands.Button_Comm2, up = ufc_commands.Button_Comm2, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm2 Button'), category = _('Up Front Control')}, Note that the Comm 2 button motion isn't animated, currently. Shoot to Kill. Play to Have Fun. Link to comment Share on other sites More sharing options...
The LT Posted December 30, 2017 Share Posted December 30, 2017 Anyone got the CMBT thrust button mapping oneliner? Is it even modeled in yet? To answer my own question {down = engine_commands.Button_CMBT, up = engine_commands.Button_CMBT, cockpit_device_id = devices.DECS, value_down=1, value_up=0, name = _('CMBT Thrust Button'), category = _('Custom Commands')}, And yes, it is modeled. My controls & seat Main controls: , BRD-N v4 Flightstick (Kreml C5 controller), TM Warthog Throttle (Kreml F3 controller), BRD-F2 Restyling Bf-109 Pedals w. damper, TrackIR5, Gametrix KW-908 (integrated into RAV4 seat) Stick grips: Thrustmaster Warthog Thrustmaster Cougar (x2) Thrustmaster F-16 FLCS BRD KG13 Standby controls: BRD-M2 Mi-8 Pedals (Ruddermaster controller) BRD-N v3 Flightstick w. exch. grip upgrade (Kreml C5 controller) Thrustmaster Cougar Throttle Pilot seat Link to comment Share on other sites More sharing options...
Chain Posted December 30, 2017 Share Posted December 30, 2017 {down = ufc_commands.Button_Comm1, up = ufc_commands.Button_Comm1, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm1 Button'), category = _('Up Front Control')}, {down = ufc_commands.Button_Comm2, up = ufc_commands.Button_Comm2, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm2 Button'), category = _('Up Front Control')},Note that the Comm 2 button motion isn't animated, currently. That's really nice of you. Thank you! System: Windows 10 | i7-7700K @ 4.5 Ghz | 32GB of RAM | Nvidia GTX 1080, 3440x1440 | DELL Ultrawide U3415W | Samsung 960 Evo M.2 and 2 TB Seagate Barracuda | TM Warthog Hotas | SLAW F-16 Pedals | Oculus Rift CV1 and HTC Vive PRO VR + High fidelity F/A-18C simpit :) Link to comment Share on other sites More sharing options...
Wicaeed Posted December 30, 2017 Share Posted December 30, 2017 Kind of a stupid question, but is there any way to increase the sensitivity of the mouse scroll for knobs like the lights/radio volume knobs? Currently 1 mouse scroll equals about 1mm of knob movement, so I have to scroll for something like 30 seconds to even get about halfway through the knobs complete rotation movement. Small nitpick... Link to comment Share on other sites More sharing options...
Tirak Posted December 30, 2017 Share Posted December 30, 2017 Kind of a stupid question, but is there any way to increase the sensitivity of the mouse scroll for knobs like the lights/radio volume knobs? Currently 1 mouse scroll equals about 1mm of knob movement, so I have to scroll for something like 30 seconds to even get about halfway through the knobs complete rotation movement. Small nitpick... You can click and drag those as well. Link to comment Share on other sites More sharing options...
Delareon Posted January 2, 2018 Share Posted January 2, 2018 Increase Mouse Sensitivity on the Buttons would be interesting, since even if you click and drag you have to do that Multiple times in order to get full Rotation.... At least on the Harrier on the other Modules it works way better i think. Link to comment Share on other sites More sharing options...
horus-DCS Posted January 6, 2018 Share Posted January 6, 2018 I have a question here. Do COMM channel selectors only work for axis? Don't they have increase/decrease values for buttons or rotary encoders? Link to comment Share on other sites More sharing options...
funkyfranky Posted January 6, 2018 Share Posted January 6, 2018 Don't they have increase/decrease values for buttons or rotary encoders? No, they don't (yet). Hope RAZBAM will add that feature :) A warrior's mission is to foster the success of others. i9-12900K | MSI RTX 3080Ti Suprim X | 128 GB Ram 3200 MHz DDR-4 | MSI MPG Edge Z690 | Samung EVO 980 Pro SSD | Virpil Stick, Throttle and Collective | MFG Crosswind | HP Reverb G2 RAT - On the Range - Rescue Helo - Recovery Tanker - Warehouse - Airboss Link to comment Share on other sites More sharing options...
metzger Posted January 13, 2018 Share Posted January 13, 2018 Zeus, F-5 (and the rest of belsimtek) is very good example how to handle switches and rotaries/position knobs, in addition include like in the m2000 (on else off) And it should be good. I thought after those years this should be already cleared and standartized. Honestly I find razbam controls setting complete mess m2000 and now harrier (regardless of on else off which is a good idea) m2000 misses any rottaries and now the harrier even the simple toggles are messed. I am not a cockpit builder but I have warthog hotas and 2 button boxes with rottaries and positional knobs to handle mostly radios and other important controls. Sent from my Redmi 4 using Tapatalk [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
smurfarama Posted January 16, 2018 Share Posted January 16, 2018 Hi guys I'm REALLY new to this, so if it is obvious, I apologise now. I have placed Vladinskys' keybind.rar into JSGME and therefore into the DCS AV8B. I have mapped the STO stop onto my Warthog China Hat, but now the STO Stop only moves 1 click at a time no matter how long I hold the China Hat forward or backwards, whereas before it would slide all the way up/down until I released the China Hat. Is there an easy way to keep all of the great benefits that the keybind.rar brings, but have my STO Stop control back to 'sliding'. Cheers. Link to comment Share on other sites More sharing options...
dannyq8 Posted January 16, 2018 Share Posted January 16, 2018 Replace {down = iCommandHelicopter_CollectiveStopper_Up, up = iCommandPlaneCollectiveStop, name = _('STO STOP UP'), category = _('Flight Control')}, {down = iCommandHelicopter_CollectiveStopper_Down, up = iCommandPlaneCollectiveStop, name = _('STO STOP DOWN'), category = _('Flight Control')}, With {pressed = iCommandHelicopter_CollectiveStopper_Up, up = iCommandPlaneCollectiveStop, name = _('STO STOP UP'), category = _('Flight Control')}, {pressed = iCommandHelicopter_CollectiveStopper_Down, up = iCommandPlaneCollectiveStop, name = _('STO STOP DOWN'), category = _('Flight Control')}, in the joystick\default.lua that you downloaded Wise men speak because they have something to say; Fools because they have to say something. Plato Link to comment Share on other sites More sharing options...
smurfarama Posted January 17, 2018 Share Posted January 17, 2018 Replace {down = iCommandHelicopter_CollectiveStopper_Up, up = iCommandPlaneCollectiveStop, name = _('STO STOP UP'), category = _('Flight Control')}, {down = iCommandHelicopter_CollectiveStopper_Down, up = iCommandPlaneCollectiveStop, name = _('STO STOP DOWN'), category = _('Flight Control')},With {pressed = iCommandHelicopter_CollectiveStopper_Up, up = iCommandPlaneCollectiveStop, name = _('STO STOP UP'), category = _('Flight Control')}, {pressed = iCommandHelicopter_CollectiveStopper_Down, up = iCommandPlaneCollectiveStop, name = _('STO STOP DOWN'), category = _('Flight Control')},in the joystick\default.lua that you downloaded dannyq8 Works great (once I had found the correct default.lua). Thanks very much. Link to comment Share on other sites More sharing options...
Soundwave197 Posted January 26, 2018 Share Posted January 26, 2018 Hi, can someone put together the lines for RWR, EXP, ECM as axis and each position of that rotary switch on the fuelpanel? I wasnt able to find the ID's in all the configs to do it myself. PC: i7 6700K - GTX980ti - ASUS Z170P D3 - 32GB DDR3 - Samsung 850Evo - 5TB HDD Displays: BenQ RL2455HM - Acer Pred. XB241H - BenQ RL2455HM Controller: Modded TM WH grip on VKB Glad.2PRO, TM WH Trottle, TM MFD`s, Saitek Rudder, 3xArduino Mega+Leonardo for AV8B panels, TIR5, Link to comment Share on other sites More sharing options...
Ruebban Posted January 28, 2018 Share Posted January 28, 2018 Hi! I'm using the AV8 rar https://drive.google.com/file/d/17bvF17DFoyLwBvGGbvCrbUgsWj0yK1Jy/view But for some reason when I use it, I can't slew the TPOD with Axis in Open Beta, as soon as i inactivate the mod, i can slew it on axis. Any clue? Link to comment Share on other sites More sharing options...
Soundwave197 Posted January 28, 2018 Share Posted January 28, 2018 Hi! I'm using the AV8 rar https://drive.google.com/file/d/17bvF17DFoyLwBvGGbvCrbUgsWj0yK1Jy/view But for some reason when I use it, I can't slew the TPOD with Axis in Open Beta, as soon as i inactivate the mod, i can slew it on axis. Any clue? They enabled slewing in the latest update but the date you are using is befor the update. I bet thats why its not working. You can try to use the 2 lines in the newest unmodified joystick.lua and put it in the modified old joystick.lua but you have to delete the old 2 lines. they should be at the last few lines. its called "--HOTAS TDC" PC: i7 6700K - GTX980ti - ASUS Z170P D3 - 32GB DDR3 - Samsung 850Evo - 5TB HDD Displays: BenQ RL2455HM - Acer Pred. XB241H - BenQ RL2455HM Controller: Modded TM WH grip on VKB Glad.2PRO, TM WH Trottle, TM MFD`s, Saitek Rudder, 3xArduino Mega+Leonardo for AV8B panels, TIR5, Link to comment Share on other sites More sharing options...
Beazle Posted February 8, 2018 Share Posted February 8, 2018 Hey guys, I don't know if it's whos dumb or it is just very complicated. I know it is a Harrier thread but I am trying to get some swticehs working on the f-5. I have read the whole thread and compared the cilckabledata.lua file of the f-5 with whats on this thread and it just seems so different and I can'T understand how to get me switches to work :( Is someone able to give me a guideline on how the f-5 2/3 way switches work? No infos is available out here :/ regards Billy Link to comment Share on other sites More sharing options...
Recommended Posts