Boat switch on Cougar

[sambucca]

Hi guys,

 

i want to map the boat switch to the dogfight switch on my cougar throttle.

 

now i can assign both boat fwd and aft to the respective Dogfight/MRM sides, but i cannot program boat switch center to the center of the dogfight switch.

 

in the F18 default.lua, you can set a 3-way switch by programming -1,0,and +1 to the switch and give each a seperate binding, but the A10 lua file looks so different, i have no clue how to do this.

 

an ideas?

[Rudel_chw]

...

an ideas?

 

I detect the button release of the dogfight button, using Foxy. The code looks like this:

 

Rem ################################################
Rem   T7-T8 : Boat Switch
Rem ################################################

BTN T7 /P   HOTAS_Boat_Switch_Aft 
            /R    HOTAS_Boat_Switch_Center 
BTN T8 /P   HOTAS_Boat_Switch_Forward 
            /R    HOTAS_Boat_Switch_Center 

 

/P is for press, /R for release

[sambucca]

Gracias Rudel,

 

I'm trying to keep my stick as universal as possible so I don't have to flash it everytime I switch between DCS and BMS, but if that works, it works..

[Frederf]

Copy the file 'Throttle - HOTAS Warthog.lua' and name it equal to the Cougar controller name and then you'll be able to use the same commands as that device.

[LeCuvier]

Frederf's suggestion is interesting.

Pro: the new file you create will not be overwritten by Update/Repair.

The default bindings from "Throttle - HOTAS Warthog.lua" will probably bind to the wrong switches, so you will have to re-do all the bindings. But that's no real disadvantage because if you use the bindings from "default.lua" you will have to create all bindings anyway.

 

The other alternative is to modify the "default.lua" using the logic from "Throttle - HOTAS Warthog.lua" but without the "combos..." stuff that provides the default bindings. You would add these 2 lines of code to "default.lua":

{down = iCommandPlane_HOTAS_BoatSwitchAft,up = iCommandPlane_HOTAS_BoatSwitchCenter, name = _('HOTAS Boat Switch Aft/Center'), category = _('HOTAS')},
{down = iCommandPlane_HOTAS_BoatSwitchForward,up = iCommandPlane_HOTAS_BoatSwitchCenter, name = _('HOTAS Boat Switch Forward/Center'), category = _('HOTAS')},

This solution is what you originally asked for.

Note: I'm using different names to reflect what these commands really do, and to avoid duplication.

Con: the Update/Repair processes restore the original files. So you need a process to back up your modified file and copy it back in after Update/Repair. Personally, I have a lot of added lines in the "default.lua" and I use OvGME to back out my modifications before a UpDate/Repair, and copy them back in afterwards.

If this would be your only modification of the "default.lua" I think that Frederf's solution is simpler and more robust.

[Frederf]

I don't know if my idea will be erased on every update or not. If updates wipe out the "default.lua" but leaves "XXX.lua" where XXX is the name of your particular controller. If it doesn't overwrite the custom file every patch then that should save a lot of headache.

 

Personally I've done all my editing on the default.lua file which requires that I unapply/reapply a JSGME mod before/after every update. It's annoying but a lot faster than editing it again every time. It would be smarter for me to use the specific lua for that controller and I am trying to do that now.

 

The difference is that default.lua will always show up regardless of which joysticks are present while XXX.lua commands will only show up if XXX is present. If that's positive or negative or neutral value (dependency on XXX present) it's up to you.

[LeCuvier]

I don't know if my idea will be erased on every update or not. ..

If your file name is different from the file names ED uses, it will not be overwritten. And it won't be erased, assuming you don't enable the option to search for extra files.