HOW TO: Display List of Cockpit Parameters For Use as ME Condition

Thought this would be helpful for mission designers. It's a technique to get a list return of the ever elusive cockpit parameters for use in the COCKPIT PARAM EQUAL TO condition.

Pre-requisites:

You must have the DCS mission running, unpaused and be occupying the airframe you wish to get the parameters from. The airframe must also have been set to 'player' in the ME.

1. Grab hold of and setup DCS witchcraft:

DCS Forum Post: https://forums.eagle.ru/showthread.php?t=126516

Github Repository: https://github.com/jboecker/dcs-witchcraft

NOTE: Unfortunately the the most recent iteration of DCSWitchcraft needs it's nodejs components manually updated for the tool to work: https://nodejs.org/en/download/

Grab the binary and copy the contents over to the relevant subfolder in your DCS Witchcraft folder - See last post in the witchcraft forum thread for details on how to.

2. add the following line to your Export.lua (found in Saved Games/DCS version/Scripts)

dofile(lfs.writedir()..[[scripts\witchcraftExport.lua]])

3. Run the previously downloaded and setup witchcraft.cmd:

you should see a CMD window open and run a load of entries...if it's setup correctly and the prerequisites are met the last lines should read:

Waiting for DCS to connect...
DCS connected.

4. point your browser to the following, it's a web GUI for the witchcraft lua program thingy-magig: http://localhost:3000/console.html

5. Type the following command and hit CTRL+ENTER to run it:

return list_cockpit_params()

6. Voila! Be presented with a complete list of the cockpit parameters available (with current variables) for the module loaded into the mission.

7. Profit.

Here's a really helpful video that guided me through the initial process:

It'll probably give more insight into what's going on, and a better explanation of the setup process. I'm just a layman repeating a lot of this parrot-fashion. Monkey see, monkey do!

I've no doubt that the tool can do/expose a lot more cool shit...but I haven't explored that too much yet.

Brick.

Thought this would be helpful for mission designers. It's a technique to get a list return of the ever elusive cockpit parameters for use in the COCKPIT PARAM EQUAL TO condition.

 

Pre-requisites:

You must have the DCS mission running, unpaused and be occupying the airframe you wish to get the parameters from. The airframe must also have been set to 'player' in the ME.

 

1. Grab hold of and setup DCS witchcraft:

DCS Forum Post: https://forums.eagle.ru/showthread.php?t=126516

Github Repository: https://github.com/jboecker/dcs-witchcraft

 

NOTE: Unfortunately the the most recent iteration of DCSWitchcraft needs it's nodejs components manually updated for the tool to work: https://nodejs.org/en/download/

 

Grab the binary and copy the contents over to the relevant subfolder in your DCS Witchcraft folder - See last post in the witchcraft forum thread for details on how to.

 

2. add the following line to your Export.lua (found in Saved Games/DCS version/Scripts)

 

dofile(lfs.writedir()..[[scripts\witchcraftExport.lua]])

 

3. Run the previously downloaded and setup witchcraft.cmd:

you should see a CMD window open and run a load of entries...if it's setup correctly and the prerequisites are met the last lines should read:

Waiting for DCS to connect...
DCS connected.

 

4. point your browser to the following, it's a web GUI for the witchcraft lua program thingy-magig: http://localhost:3000/console.html

 

5. Type the following command and hit CTRL+ENTER to run it:

return list_cockpit_params()

 

6. Voila! Be presented with a complete list of the cockpit parameters available (with current variables) for the module loaded into the mission.

 

7. Profit.

 

Here's a really helpful video that guided me through the initial process:

It'll probably give more insight into what's going on, and a better explanation of the setup process. I'm just a layman repeating a lot of this parrot-fashion. Monkey see, monkey do!

 

I've no doubt that the tool can do/expose a lot more cool shit...but I haven't explored that too much yet.

 

Brick.

luaresult { name: '1566275531944',

result:

'[string "1566275531944"]:1: attempt to call global \'list_cockpit_params\' (a nil value)',

success: false,

type: 'luaresult' }

Any idea ?

Hi all,

I have the same issue! Anyone have the clue to solve that?

Did you manage to fix edineygomes?

Thanks

Hornet