Documentation

[Coding]

I have studied informatics, wrote a few mods for  ArmA 3, wrote some Android-Apps, code for fun and just did not get involved in coding with DCS for a single reason.

I do not want to offend someone personal but the documentation of the (MissionEditor-)API is a joke.

Quote

X: COCKPIT HIGHLIGHT ELEMENT – enables a cockpit highlight of the specified cockpit control (switch, button, knob, etc.).
• ID – sets the ID of the highlight. The ID can be referenced by other triggers to evaluate the status of or remove the highlight.
• ELEM NAME (element name) – sets the name of the cockpit control to highlight. Clickable cockpit functions (switches, buttons, knobs, etc.) are described in Scripts\Aircrafts\Aircraft Name\Cockpit\clickabledata.lua.
• SIZE OF BOX – sets the span of the highlight in meters. A setting of ‘0’ will automatically conform the highlight to the 3D shape of the cockpit control.

Avionics plugin is not even mentioned.

The path to the .lua file is wrong.

AND...

Quote

Clickable cockpit functions (switches, buttons, knobs, etc.) are described in Scripts\Aircrafts\Aircraft Name\Cockpit\clickabledata.lua.

You have to read that twice. (or more)

I do not know what you mean with "described"...

This is what the "description" actually looks like:

Quote

elements["pnt_132"]        = short_way_button(_("UFC Function Selector Pushbutton, D/L"),            devices.UFC, UFC_commands.FuncSwDL,        132)

I had to guess multiple times to figure out what the "ELEM NAME" was.

Let me tell you something.

You might ignore it if you want to but this is my feedback which aims to improve your product.

Eventually I might have reverseengineered some websites.

But coding for DCS feels more like hacking than actually hacking.

Hacking is just coding.

coding for DCS...

Just dont do that.

[draconus]

"Coding", hacking? Dude, it's simple lua and plain text files, you'll figure it out. If not the community will gladly help:

https://forums.eagle.ru/forum/69-mods-and-apps/