Jump to content

Recommended Posts

Posted

I am very new to editing the LUA files for controllers.  I've been reading on the forums, understanding that they can be editing to use on on/off switch to control a toggle in game.  I just got the two WINWING control panels and everything works very well except the hook bypass and launch bar.  The two issues are:

 

1. The launch bar mostly works.  For some reason the launch bar is starting "extended".  If the switch is left in the extended position physically, then all is well.  But the bar then has to be retracted in C&D.  I don't know what happened in this process, as prior to connecting these panels the launch bar always started "retracted".  I an also click the virtual cockpit switch to "sync" if the physical hardware starts out of phase.  This switch is a two position switch, but the command only has a toggle extend/retract.  Anyone have any ideas why the launch bar default to extended now?  Or how to change this.

 

2. The hook bypass switch is "on" at the field setting.  The command is a toggle, so ideally it would toggle on release as well to keep the state in sync. 

 

And in a really ideal world, there would be separate commands for switch state so we could ensure controls were in sync.  These are the relevant sections of the WINWING***.diff.lua file:

 

        ["d3008pnilu3008cd5vd1vpnilvu0"] = {
            ["added"] = {
                [1] = {
                    ["key"] = "JOY_BTN8",
                },
                [2] = {
                    ["key"] = "JOY_BTN7",
                },
            },
            ["name"] = "Launch Bar Control Switch - EXTEND/RETRACT",
        },
        ["d3009pnilu3009cd9vd1vpnilvu0"] = {
            ["added"] = {
                [1] = {
                    ["key"] = "JOY_BTN20",
                },
            },
            ["name"] = "HOOK BYPASS Switch - FIELD/CARRIER",

 

From my reading, the bypass section needs something added with a -1, but I'm a little unsure where to add this.  For the launch bar, I have less of an idea. 

 

Thanks for any help!

Posted

Hi, I can’t help with the editing, but I can point you to a file you can install to sort this ......search my post in the winwing section on the subject, a guy named Fox2 supplied a pre edited .lua file. I guess you can look and see inside how he did what you want.......

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.

CVW-17 Profile Background VFA-34.png

Posted (edited)

I have those panels and have come across this as well and it can be addressed without lua editing. In the SimAppPro software you can go to the Key Binding tab. Then click the take off panel, then DCS and then the F18C. Then you will see bottom right where it says there are some profiles available for use. I use the profile for 100% correct mapping and this fixed the hook bypass switch issue. I still get an issue with raising the launch bar so I just ensure my switch is up and then use my VR controller to raise it to match in the virtual cockpit at the start of the mission and it is fine after that. This one thing is a bit of an anomaly or bug, I guess, and maybe will be sorted soon. Other then that one thing everything else works perfectly as advertised. I hope this points you towards a solution you are happy with.

Edited by Oozler
Posted

Thank you for the replies.  Reading further in the thread referenced by markturner1960, I realized editing the commands in default.lua can create separate "up" and "down" commands instead of toggles.  I had not read this nuance previously.  Once I realized this, the edits were fairly quick and then I just remapped the controls through the DCS controller menus. 

 

Unfortunately this is going to get reset frequently in DCS updates.  I will keep a backup of the file, but this may change with time.  It would seem like DCS could be well served by an "advanced controller setup" or "home cockpit controls" option in the menus that automatically generates on and off state controls rather than toggles alone.  It would keep it cleaner for the more casual player (I assume that's why things are setup as they are), but allow an easy option without editing files themselves. 

Posted

Yes, only issue is any update, you need to copy the file in again. Glad it helped

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.

CVW-17 Profile Background VFA-34.png

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...