Jump to content

DCS Cockpit Arguments


Mt5_Roie
 Share

Recommended Posts

Is there a master list of DSC Cockpit arguments somewhere? I'm working on creating a cockpit and I found the following arguments from the wunderluft code:

 

PlanePickleOn = 350,

PlanePickleOff = 351,

PlaneFireOn = 84,

PlaneFireOff = 85,

 

I also found the ones for gear up and down, flaps up and down. But I'm looking for the rest of them. I'm trying to find the opens for speedbrakes and the canopy. but would like to see the master list to see what is built into to DCS that I have to use.

Coder - Oculus Rift Guy - Court Jester

Link to comment
Share on other sites

this is the list I've found so Far using EDMViewer, But I cant sit in ModelViewer Toggling ARGs right now:

 

Arg # Mesh Movement

1

2

3

4

5

6

7 Canopy 0.0 Close, .900 Open, .910 No Draw

8 Left Throttle 0.0 Off, 1.0 Full

9 Right Throttle 0.0 Off, 1.0 Full

10 Stick Pitch 1.0 Full Aft, -1.0 Full Forward

11 Stick Roll 1.0 Full Right, -1.0 Full Left

12 Climb Gauge 1.0 Max Climb, -1.0 Max Dive

13 APU % 1.0 Max Power, 0.0 Zero Power

14 APU EGT 1.0 MAX, 0.0 Min

15

16

17 ADI Ball Pitch -1.0 Max Climb, 1.0 Max Dive

18 ADI Ball Roll -1.0 Max Roll Left, 1.0 Max Roll Right

19 ADI Ball Flag 0.0 retracted, 1.0 Deployed

20 ADI Vert Line -1.0 Max Left, 1.0 Max Right

21 ADi Hor Line -1.0 Max Down, 1.0 Max Up

22 ADI Knob -1.0 Max Counter Clock Wise, 1.0 Max Clockwise

23

24

 

712 Canopy Switch -1.0 Close, 1.0 Open

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill,

X470 Taichi Ultimate, R7970 Lightning @ 1.2 / 6 GHz Memory

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment
Share on other sites

AFAIK, you can assign any argument number for your cockpit switch/buttons - clickabledata.lua

 

List of basic commands for gear, brakes, lights etc etc you can find at DCS World\Config\Export\export.lua

 

So basically, argument number is not standardized for cockpit animation, but list of basic action commands is standard - this number you have to use at your_device.lua

Link to comment
Share on other sites

this is the list I've found so Far using EDMViewer, But I cant sit in ModelViewer Toggling ARGs right now:

 

Arg # Mesh Movement

1

2

3

4

5

6

7 Canopy 0.0 Close, .900 Open, .910 No Draw

8 Left Throttle 0.0 Off, 1.0 Full

9 Right Throttle 0.0 Off, 1.0 Full

10 Stick Pitch 1.0 Full Aft, -1.0 Full Forward

11 Stick Roll 1.0 Full Right, -1.0 Full Left

12 Climb Gauge 1.0 Max Climb, -1.0 Max Dive

13 APU % 1.0 Max Power, 0.0 Zero Power

14 APU EGT 1.0 MAX, 0.0 Min

15

16

17 ADI Ball Pitch -1.0 Max Climb, 1.0 Max Dive

18 ADI Ball Roll -1.0 Max Roll Left, 1.0 Max Roll Right

19 ADI Ball Flag 0.0 retracted, 1.0 Deployed

20 ADI Vert Line -1.0 Max Left, 1.0 Max Right

21 ADi Hor Line -1.0 Max Down, 1.0 Max Up

22 ADI Knob -1.0 Max Counter Clock Wise, 1.0 Max Clockwise

23

24

 

712 Canopy Switch -1.0 Close, 1.0 Open

 

When I was testing it from the cockpit I basiclly had a counter that goes up by one everytime I press the button. I found that 8-14 activates external views. So it might be different from the EDModelViewer shows.

 

I'll look at the export file....thanks.

Coder - Oculus Rift Guy - Court Jester

Link to comment
Share on other sites

yeah, those arent ARG Numbers, they are command numbers..

 

which are in the export.lua

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill,

X470 Taichi Ultimate, R7970 Lightning @ 1.2 / 6 GHz Memory

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment
Share on other sites

Exactly. There are no such thing as cockpit arguments anymore... you define them yourself. For example, I'm using 0-100 for mechanical parts, 101-200 for console switches, etc. Animation can be defined in mainpanel_init and switch action is done via clickabledata and a device of your choosing.

Link to comment
Share on other sites

Thanks guys. Still learning with the Wunderluft example and got a simple hud set up and working on how to set up a cockpit with working buttons. Been having good success so far, but still can't get canopy to work right.

Coder - Oculus Rift Guy - Court Jester

Link to comment
Share on other sites

So I'm still having issues trying to get a tailhook to work. In the EDModelViewer the animation for the tailhook is arg 25 from 0 to 1. So in my clickabledata.lau I have:

elements["PNT-10"]			= {class = {class_type.BTN}, hint = "", device = devices.AVIONICS, action = {device_commands.Button_10}, stop_action = {device_commands.Button_19}, arg = {25}, arg_value = {1.0}, arg_lim = {{0.0, 1.0}}, use_release_message = {true} }							 

 

PNT-10 is the cockpit button I want to link it to. It's linked to the AVIONICS device. Which has the following code:

  if command == 3010 then
print("Tailhook Pressed")
dispatch_action(nil,69)
 end 

 

When the button is pressed, I get the log portion that says it was pressed, but tailhook doesn't go down. I do see that it seems to run the animation on the cockpit that is tied to animation arg 25 for it though.


Edited by roiegat

Coder - Oculus Rift Guy - Court Jester

Link to comment
Share on other sites

Right Sevas...

AFAIK, you can assign any argument number for your cockpit switch/buttons - clickabledata.lua

 

List of basic commands for gear, brakes, lights etc etc you can find at DCS World\Config\Export\export.lua

 

So basically, argument number is not standardized for cockpit animation, but list of basic action commands is standard - this number you have to use at your_device.lua

__________________

 

Here is my buttons and switch for this moment and i upgrade every day...

 

Battery 1

Battery 2

Inventor

Fuel Pump

AC Generator

DC Generator

ENG System

Engine selector

Engine start button

Canopy

Gear

Flaps

Refueling Boom

..........

Link to comment
Share on other sites

So I'm still having issues trying to get a tailhook to work. In the EDModelViewer the animation for the tailhook is arg 25 from 0 to 1.

 

That's not a cockpit argument, now is it? External arguments are currently limited. Only solution is to wait for a future update.

Link to comment
Share on other sites

That's not a cockpit argument, now is it? External arguments are currently limited. Only solution is to wait for a future update.

 

 

Aaron,

 

Thanks again for your wisdom. I guess the wording I used was a bit off. The numbers I was looking for were actually in the export.lua so that helped a lot. I also got confused between cockpit arguments and external arguments. Taking baby learning steps here.

 

The good news is last night I was finally able to map the stick, rudder, throttle to their correct animations, which is awesome. Plus I started getting some gauges to work and had great success there.

 

So thanks to everyone who's helped out.

Coder - Oculus Rift Guy - Court Jester

Link to comment
Share on other sites

  • 9 years later...

Does anybody know what's correct argument value for F18 HMD brightness knob?

The one that is used  (136)  in SIM cockpit  app https://simvc.com/ isn't correct because it doesnt work...

  panel:get_argument_value(136) --[[ 5 HMD OFF/BRT Knob ]],

[sIGPIC][/sIGPIC]

Pilot from Croatia

Link to comment
Share on other sites

38 minutes ago, hreich said:

Does anybody know what's correct argument value for F18 HMD brightness knob?

The one that is used  (136)  in SIM cockpit  app https://simvc.com/ isn't correct because it doesnt work...

  panel:get_argument_value(136) --[[ 5 HMD OFF/BRT Knob ]],

It is 58.

Intel® Core III Xeon Duo CPU E8600 @ 3.33GHz - 4 Mo RAM - GeForce 1080TI - Monitor DELL E190S - SB Audigy - HOTAS Warthog

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

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