Manual Tweak - keybind addition for Radar On / Standby on Hotas / Keyboard

[Rlaxoxo]

This was posted on Reddit few moments ago

 

 

With the little tweak it added the option for Radar On/Standby

 

All Credits to /u/Deezle666

 

Easy addition via mod (JSMGE compatable)

 

https://www.dropbox.com/s/j65fb95gmmodetd/Mirage%202000C%20--%20Keybinds%20-%20Radar%20On%20%26%20Standby%20fix.rar?dl=0

 

UPDATE:

Fixed the broken path I've neglected to check before I uploaded and added couple of other binds that were mentioned in comments below

__________________________________________________________________________________________________________________

 

UPDATE 2:

 

Added all the binds and put them together for Keyboard and HOTAS Joysticks

 

For more info visit the following link

 

 

UPDATE 3: Added Even more binds like: Emergency Jettison, Radar Grid Selector, Extra Switches, Press and Hold binds, ECM Box binds ... etc

 

Check the reddit link for more info

_____________

Edited January 10, 2016 by Rlaxoxo

[0xDEADBEEF]

so good! thank you!

Edited January 6, 2016 by 0xDEADBEEF

[Deezle]

I've also been doing the radar azimuth and scan lines, selective jettison, ect, I can easily make them work with Warthog 2 and 3 position switches but I'm not sure how to make them incremental/toggleable for those who have other controllers. So I just posted that one for now.

[Rlaxoxo]

I've also been doing the radar azimuth and scan lines, selective jettison, ect, I can easily make them work with Warthog 2 and 3 position switches but I'm not sure how to make them incremental/toggleable for those who have other controllers. So I just posted that one for now.

 

<3

[0xDEADBEEF]

I've also been doing the radar azimuth and scan lines, selective jettison, ect, I can easily make them work with Warthog 2 and 3 position switches but I'm not sure how to make them incremental/toggleable for those who have other controllers. So I just posted that one for now.

 

ohhh would you mind posting these lines of code here? that would be fantastic!!

[Deezle]

Here they are for now. These work with 2 and 3 postion toggles, the center (or off) position of the switch is taken care of when you map the other postions.

 

{down = 3249, up = 3249, value_up = 0, value_down =1,  cockpit_device_id = 6,    name = 'Selective Jettison', category = 'Armament Panel (PCA)'},
{down = 3506, up = 3506, cockpit_device_id = 11, value_up=.5, value_down = 1, name = 'Radar Azimuth Narrow', category = 'Radar'},
{down = 3506, up = 3506, cockpit_device_id = 11, value_up=.5, value_down = 0, name = 'Radar Azimuth Wide', category = 'Radar'},
{down = 3502, up = 3502, cockpit_device_id = 11, value_up=.5, value_down = 1, name = 'Radar Scan 1 Line', category = 'Radar'},
{down = 3502, up = 3502, cockpit_device_id = 11, value_up=.5, value_down = 0, name = 'Radar Scan 4 Lines', category = 'Radar'},

[0xDEADBEEF]

<3

[0xDEADBEEF]

slective jettison doesnt seem to work for me?

[Deezle]

You'll have to click the cover open.

[0xDEADBEEF]

You'll have to click the cover open.

 

Boom, i need this little push, haha!

 

please let me contribute the jettison safetycover switch up/down capable. You guys made me look up the functions :)

 

{down = 3248, up = 3248, value_up = 1, value_down = 0,  cockpit_device_id = 6,    name = 'Selective Jettison Safety Cover', category = 'Armament Panel (PCA)'},

 

this makes this plane a lot more enjoyable :)

Edited January 6, 2016 by 0xDEADBEEF

[Deezle]

Yeah I thought about doing that one too, but I just flick the cover once and leave it up, not worried about accidentally hitting the switch in a fake airplane :thumbup:

[ody81]

Whaaaa?

Is it possible I could make a next/prev binding for the Mig-21's weapon rotary by doing this?

[TomCatMucDe]

Thanks a lot guys,

 

here are my changes to add 2 position switches for FBW G limiter and Master Arm:

{down = 3234, up = 3234, value_up = 0, value_down = 1,  cockpit_device_id = 6,    name = 'Master Arm', category = 'Alternate'},
value_up= 1, value_down = 0, name = 'Air-to-Air/Stores G Limiter', category = 'Alternate'},

For the Master Arm to work you need also to exchange the line 380 in the file clickabldate.lua with this line

elements["PTN_234"] = default_2_position_tumb(_("Master Arm Switch"), devices.PCA_PPA, device_commands.Button_234, 234)

Also if you want to have the Radar Stanby/On in a 2 position switch like me you can use this

{down = 3486, up = 3486, cockpit_device_id = 11, value_up= 1, value_down = .66, name = 'Radar On / Standby', category = 'Alternate'},

I will try to get the Airbrakes and landing gears to work later on.

Edited January 6, 2016 by TomCatMucDe

[ImTooLazy]

Since I'm new with the warthog, is it possible to make a simpe toggle on/off switch without tweaking ? For instance, the master arm... I have to engage it twice for turning it off. It doesn't really matter for AP since you have to arm it...

 

EDIT : okay I'm stupid, didn't read TomCatMucDe

Edited January 6, 2016 by ImTooLazy

[0xDEADBEEF]

I will try to get the Airbrakes and landing gears to work later on.

 

I solved the airbrakes with a simple double-on toggle:

{down = iCommandPlaneAirBrake, up = iCommandPlaneAirBrake, name = _('Toggle Airbrake'), category = _('Systems')},

 

did anyone get the jammer going? I could not even assign a working button :( button is 606 and cathegory 12

[Rlaxoxo]

Anyone know how to make Throttle usable on keyboard?

[TomCatMucDe]

I solved the airbrakes with a simple double-on toggle:

{down = iCommandPlaneAirBrake, up = iCommandPlaneAirBrake, name = _('Toggle Airbrake'), category = _('Systems')},

 

did anyone get the jammer going? I could not even assign a working button :( button is 606 and cathegory 12

 

your airbrakes work like a charm.

 

here is how you get the Jammer, the category is 12 as you said but you have to add always +1 because of the counter in the beginning of the file. so cockpit_device_id should 13. I tested it, it works.

 

{down = 3606, up = 3606, cockpit_device_id = 13, value_up= 0, value_down = .5 , name = 'Jammer', category = 'Alternate'},

[0xDEADBEEF]

here is how you get the Jammer, the category is 12 as you said but you have to add always +1 because of the counter in the beginning of the file. so cockpit_device_id should 13. I tested it, it works.

 

there you go! I thought it was Device 11, EW_RWR, and added a 1 to that ... thanks!

[Greekbull]

Can we assign keystrokes to these as well? I'm working on a helios profile with working switches. And of course with a clickable cockpit they didn't assign many functions key commands. If we can get key commands for the front panel Hud controls etc I can mail those into the helios profile and distribute...also was going to use the English cockpit for an even better setup.

[Deezle]

Can we assign keystrokes to these as well? I'm working on a helios profile with working switches. And of course with a clickable cockpit they didn't assign many functions key commands. If we can get key commands for the front panel Hud controls etc I can mail those into the helios profile and distribute...also was going to use the English cockpit for an even better setup.

If you place these lines in the default.lua located in the keyboard folder they will be mapable to the keyboard.

[0xDEADBEEF]

Some more goodies, the Engine Start Panel:

 

{down = 3645, up = 3645, cockpit_device_id = 7, value_up=1, value_down=0, name = "Start Button Safety Cover", category = "Engine"},
{down = 3646, up = 3646, cockpit_device_id = 7, value_up=0, value_down=1, name = "Starter Fuel Pump", category = "Engine"},
{down = 3647, up = 3647, cockpit_device_id = 4, value_up=0, value_down=1, name = "Left Fuel Boost Pump", category = "Engine"},
{down = 3648, up = 3648, cockpit_device_id = 4, value_up=0, value_down=1, name = "Right Fuel Boost Pump", category = "Engine"},
{down = 3649, up = 3649, cockpit_device_id = 7, value_up=1, value_down=0, name = "Engine Start Switch", category = "Engine"},
{down = 3650, up = 3650, cockpit_device_id = 7, value_up=0.5, value_down=0, name = "Ventilation Selector Switch", category = "Engine"},
{down = 3467, up = 3467, cockpit_device_id = 7, value_up=0, value_down=1, name = "Engine Shutdown Switch", category = "Engine"},

[Rlaxoxo]

Some more goodies, the Engine Start Panel:

 

{down = 3645, up = 3645, cockpit_device_id = 7, value_up=1, value_down=0, name = "Start Button Safety Cover", category = "Engine"},
{down = 3646, up = 3646, cockpit_device_id = 7, value_up=0, value_down=1, name = "Starter Fuel Pump", category = "Engine"},
{down = 3647, up = 3647, cockpit_device_id = 4, value_up=0, value_down=1, name = "Left Fuel Boost Pump", category = "Engine"},
{down = 3648, up = 3648, cockpit_device_id = 4, value_up=0, value_down=1, name = "Right Fuel Boost Pump", category = "Engine"},
{down = 3649, up = 3649, cockpit_device_id = 7, value_up=1, value_down=0, name = "Engine Start Switch", category = "Engine"},
{down = 3650, up = 3650, cockpit_device_id = 7, value_up=0.5, value_down=0, name = "Ventilation Selector Switch", category = "Engine"},
{down = 3467, up = 3467, cockpit_device_id = 7, value_up=0, value_down=1, name = "Engine Shutdown Switch", category = "Engine"},

 

How do you find the ID number for the command?

[0xDEADBEEF]

found the file through the notepad++ search function (i made it search the whole folder), its in the clickabledata.lua in the m200s cockpit folder.

[Rlaxoxo]

Updated the the thread with link for Keyboard bindings etc ...

[Rlaxoxo]

found the file through the notepad++ search function (i made it search the whole folder), its in the clickabledata.lua in the m200s cockpit folder.

 

Could you pls tell me what does "{down = 3645, up = 3645," this number represent and I tried looking trough clickabledata.lua

 

And I Can't really tell where the cockpit_device_id = 7 is?

 

Mind explaining this if you can?