LUA scripting for 3 way toggles

[Baldawg]

SOOOOO.... i've been enjoying the A10 and have my simpit set up pretty well but my main issue is the 3 way toggles. i have on - off - on toggles but they didn't perform as i thought so i bought on - on - on switches and they work but when i go from say switch 1 to switch 2 to switch 3 it moves and the sim switch moves as it should. However, if i go from position 3 to position 2 it doesn't move. I know there is programming to be done but have no idea what i need to do. i have notepad ++ and have looked through the lua files for the warthog to compare. Is anyone a "GURU" in lua programming around that might be able to lead the blind to the light if you know what i mean???

Edited April 12, 2015 by Baldawg

[FSFIan]

You can map the panels connected to your Leo Bodnar board through Helios. Setting up the bindings in your Helios profile can be annoying, but you only have to do it once.

 

You can also use DCS-BIOS, which is quicker to set up, but currently has no way to interface with USB joysticks, so it's probably a better fit for new panels if you don't want to mess around with (and buy Arduino boards for) the existing ones.

 

I would not go the route of editing the input Lua files, because that way you may have to constantly react to changes in DCS: World. You'd also have to look at the A-10C's clickabledata.lua file for each switch to find out the correct command IDs and arguments, because internally, some switches work differently from others.

Edited April 12, 2015 by [FSF]Ian

[Hansolo]

Hi Baldawg,

 

Although I agree with Ian to go with DCS-BIOS you can do it via the Joystick.lua file. I strongly recommend you use JSGME to exchange the modded joystick.lua file as it makes it easier to install after DCS has been updated.

 

Here is a link to JSGME if you aren't familiar with it already; http://forums.eagle.ru/showthread.php?t=98607

 

As for the modding of the joystick.lua file please take a look here; http://forums.eagle.ru/showpost.php?p=2017801&postcount=52

 

It should give you an idea of what is done. I'll update this post later today with the joystick.lua I am currently using myself :-)

 

Cheers

Hans

[Baldawg]

@Hans, thanks for this....to be honest I forgot posted this thread,

@Ian ...... disregard the post on the other thread from you to me. The answer to my question, my friend, is answered in here.

With that said, does anyone have the time or know the guru with patience to step me through the Lua editing process. I understand the concept, have notepad ++, and novice level programming skills. I do see in the coding how the inverter switch works appropriately from test to off. Once I can get that one working from stby to off then everyone else will be a breeze.

Edited October 2, 2015 by Baldawg

[Hansolo]

Hi Baldawg

 

Sorry I think I completely forgot about the upload. Anyway here is my current (1.2.6);

https://www.dropbox.com/s/gauju5bvxdrszuh/HMA%20joystick%20default%20-%20NEW.rar?dl=0

 

If you load it with the JSGME then it should be plug n' play. All you need is to map your joystick inputs.

 

If you run into any problems just let me know :-)

 

Cheers

Hans

[Baldawg]

:thumbup:

this definitely makes the switches perform as they should.....however it has removed my ability to program buttons to certain switches in game (ie the lighting panel.) I cant program my rotary encoders to adjust the formation lights, console lights etc etc. In theory, could i copy and paste the edited lines for the 3 way toggles into the original default.lua and preserve the code for the other buttons that i don't want changed from the original?

[Baldawg]

i tried adding your edits to my original to no avail..... i guess there is more to it then i'm seeing. The only switches i'm concerned about now are the Landing/Taxi Light, Position Lights, Inverter switch and IFFCC switch. I dont have any other 3ways setup (ie on the master arm laser etc etc on the armament panel) due to this hurdle with 3 way toggles. I feel that i'm real close but anything i try to do with my original barring taking coding for the non programmable buttons from my original and adding it to your edited version i'm at a loss.. hope that makes sense. Im open for thoughts questions guidance or a boot to the face.

[Hansolo]

this definitely makes the switches perform as they should.....however it has removed my ability to program buttons to certain switches in game (ie the lighting panel.)

When you say buttons I guess you mean push buttons as the keyboard bindings are in another file. In that case your should be able to use the original file, find the bindings for Landing/Taxi light, Position light, Inverter switch and IFFCC, replace these lines with matching lines from my modified one. So it's not copy paste, but copy and replace.

 

 

i tried adding your edits to my original to no avail..... i guess there is more to it then i'm seeing. The only switches i'm concerned about now are the Landing/Taxi Light, Position Lights, Inverter switch and IFFCC switch. I dont have any other 3ways setup (ie on the master arm laser etc etc on the armament panel) due to this hurdle with 3 way toggles. I feel that i'm real close but anything i try to do with my original barring taking coding for the non programmable buttons from my original and adding it to your edited version i'm at a loss.. hope that makes sense. Im open for thoughts questions guidance or a boot to the face.

 

I made this explanation based on others findings and it should still be valid;

 

All the files you need are located here:

C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\A-10C\Cockpit\Scripts

 

The + 3000 is defined in command_defs.lua line 492 an onwards.

 

When you want to do the APU GEN you need to locate it in clickabledata.lua:

elements["PTR-EPP-APU-GEN-PWR"] = {class = {class_type.TUMB, class_type.TUMB}, hint = _("APU Generator On/Off"), device = devices.ELEC_INTERFACE, action = {device_commands.Button_1 ,device_commands.Button_1}, arg = {241,241}, arg_value = {-1,1}, arg_lim = {{0,1},{0,1}},updatable = true}

 

devices.ELEC_INTERFACE is found in devices.lua line 8 as counter() -- 1. Here you note down 1 (one) as you need it for cockpit_device_ID=1

 

device_commands.Button_1 we already found in comman_defs.lua to be + 3000, thus down = 3001 and up = 3001

 

{0,1} are the values for up=unactivated and down=activated thus value_down=1 and value_up=0

 

Then you have the full line:

{combos = {{key = "JOY_BTN89"}}, down = 3001, up = 3001, cockpit_device_id = 1, value_down = 1, value_up = 0, name = "APU generator power", category = "Electrical power control panel"}

 

The orange text is the original from the joystick.lua. I am pretty sure this is what it is displayed as in the game Option - Controls

 

If it doesn't make any sense please let me know :-)

 

Cheers

Hans

[Baldawg]

I did copy and paste the modified code and removed the original code but that's why we are still chatting I'm not getting the results that your lua file gives me. I'm not a programmer so looking at the above code only makes my brain hurt a little. Either I'm missing a step or there is a particular why to take your modified code and put it into the original default.lua that I have. It seems simple enough but somewhere DCS doesn't like what I'm doing to it.

 

Just so we are on the same page. I only copied the individual lines of code from your lua to mine. I was working with the inverter codes. I did not copy paste your entire lua into my default.lua. I just thought that may be what I need to do however there is a lot of the coding in your lua I don't need.

Edited October 7, 2015 by Baldawg

[Hansolo]

Do not worry. I am not a programmer either :-)

 

Just to make sure I am not overlooking anything. Have you setup the Leo Bodnar software to handle the encoders? Its available at the Loe Bodnar site.

It's not enough to simply connect the the encoders to the board. There need to be a little piece of software in between the board and the DCS to enterpret the the signals. There is one for BBI-32 and one for the BU0836X.

 

Cheers

Hans

[Baldawg]

Yes i've been using the encoders on other modules as well as the A10....just to let you know a fellow squad mate and i edited my default.lua in the 1.5 beta and viola....its working....we fly 1.2.6 in our squadron and for some reason the edits aren't working properly on that version so........i got it to work and 3 way toggles are functional.....thank you so much for being a good sport and pushing me to not give up.

[Hansolo]

Excellent Baldawg :thumbup: I do not understand why you can't get it to work in 1.2.6 as mine are from 1.2.6. We haven't switched either by the way :smilewink:

Anyway I am glad you got it to work if only in 1.5.

 

And my pleasure. Happy hunting Sir

 

Cheers

Hans

[Baldawg]

just wanted to update you on this....as for 1.2.16 i got it working by editing the .diff.lua files in the saved games folder. however im unable to edit anything for the F-15c in 1.5.1. niether the default lua nor the diff.lua give results or they give negative results.