Extension "DKS"
Digital Kneeboard Simulator (DKS) is a planning and debrief suite for
DCS squadrons. This extension installs the DKS exporter on your instance. The exporter records your missions for DKS
(3D debriefs, LSO grades, live ATC/GCI views) and replaces Tacview: once it is installed, DCSServerBot disables the
Tacview extension for that instance and turns Tacview off in its options. The exporter takes over what Tacview did
there:
- Tacview real-time telemetry, on Tacview's port and with its password (/help lists the port in the firewall script
under this extension),
- Tacview files (.acmi), in Tacview's export folder.
Warning
What the Tacview extension did on its own is gone for that instance: uploading Tacview files to a channel or folder
(target), /tacview commands, and the tournament plugin's Tacview handling. Tacview's files stay installed, so you
can switch back by disabling DKS and enabling Tacview.
Note
Earlier versions of this extension installed the DKS add-on for Tacview (a weather exporter). It is retired and removed (Tacview's own tacview.dll is put back). Use the DKS exporter instead: get an install code (below). Until you do, DKS stays inactive and says so once each time DCSServerBot starts.
Configuration
There are three ways. All of them need the server's install code from DKS: open your server's page in DKS (Settings → Servers), and press DCSServerBot next to the exporter.
- From DKS, in one click. If your bot is linked to DKS (plugin DKS), the
server is linked to your bot's server, and an Admin allowed it with
/dks install_permission, press Install. DKS asks your bot to install the exporter. - In Discord. Run
/extension enable, pick your server andDKS, and paste the install code. If DKS was enabled before (the earlier weather exporter), it isn't offered in the list: typeDKS. - In nodes.yaml:
# config/nodes.yaml MyNode: # ... instances: DCS.dcs_serverrelease: extensions: DKS: enabled: true key: "dks1...." # the install code
The exporter starts with the next server start. DCSServerBot downloads it once, from DKS over https only, and from
then on the exporter updates itself. It only installs versions signed with DKS's release key, so autoupdate doesn't
apply.
Settings set on the server's page in DKS ("Set in DKS") win over the ones carried over from Tacview.
The install code holds the server's key. Keep it private. It is stored in nodes.yaml, and at log level DEBUG it shows
up in the bot's log when a master node configures the extension on an agent. After New key in DKS, install again
(or paste the new code): DCSServerBot rewrites Config\DKS-Telemetry.cfg from nodes.yaml at every start.
Uninstall
Stop the server, then disable the extension with /extension disable (DCS keeps the exporter's files in use while
it runs). Recordings that were not uploaded yet stay in Saved Games\<instance>\DKS\telemetry.
Configuration reference
| Key | Type | Description | Example |
|---|---|---|---|
enabled |
bool | Whether the DKS exporter is installed on this instance. | true |
name |
str | The name shown for the extension. (range: min 1) | DKS |
hidden |
bool | Hide the extension in the server status. | false |
autoupdate |
bool | Not used. The exporter updates itself (signed releases). Kept so older configurations stay valid. | false |
key |
str | The install code from your server's page in DKS. (range: min 1) | dks1.eyJka3NVcmwiOi... |