APP

PYTHON TOOLS

Current Development Status – Aviation Map & DataPad Features
(February 2026)

I'm currently not actively working on the Aviation Map, live DataPad / telemetry, or tactical units features, because I do not have DCS World installed right now and cannot verify / test > whether changes still work or break functionality.

The topic will definitely be continued in the future once I have a proper DCS test environment again.

If anyone is interested in actively contributing, testing, or submitting pull requests in the meantime → very welcome!
I will happily look at everything, review code / changes, and give feedback in English.

Thanks for your understanding and patience 🙏
o7

Screenshots • Demo Videos

InteractiveChecklists is an Android application for viewing and interacting with Markdown and PDF checklists. It is built with Jetpack Compose and follows an MVVM-style architecture. It is designed to be extensible with an interactive aviation map featuring live DCS data integration, tactical markers, and dynamic route and pattern calculation. Runway heading–based approach visualization and real-time map updates enable enhanced situational awareness during flight operations.

Development status: This repository is a development version and not an official release. The app is functional but under active development and may contain experimental features.

Note: A preview APK for version 1.1 is planned. If you are not familiar with Android Studio or building apps from source, please wait for the official preview release to test the app.

Table of Contents

• Features
• Screenshots
• Demo Videos
• Installation
• System Requirements
• How to Build & Run
• Key Components
• Contributing
• Support & Contact
• FAQ
• Acknowledgements & Credits
• License

• Unified File System: Manage files from bundled assets and internal storage in a single hierarchical view.

• Multilanguage Support: The app supports English, Spanish and German. You can switch the language in the Settings menu. All UI text is available in English.

• Multi-Tab System: Open multiple documents (MD/PDF) with a scrollable tab bar, quick tab switcher, swipe navigation, and tab persistence.

• PDF Viewer: PDF viewer with annotations (draw/highlight/erase), pinch-to-zoom, page snapping, and color inversion.

• Interactive Markdown Checklists: Stateful checkboxes and collapsible sections for interactive checklists.

• Tagging System: Assign tags to files for filtering and organization.

• QuickNotes: Persistent notes powered by Room, with search, autosave, and markdown support.

• Data Persistence: Stores user preferences, annotations, shortcuts, tags, and open tabs locally.

• Aviation Map (experimental): OpenStreetMap-based map viewer with live aircraft position tracking from the DataPad stream. Adds a MapViewer tab showing aircraft position, heading, altitude and basic overlays — see docs/EN/features/AVIATION_MAP_FEATURE.md for details and configuration.

• DataPad (experimental): Live flight telemetry display (UDP) for DCS World. Streams aircraft telemetry to the app for realtime status and popup details — see docs/EN/features/DATAPAD_FEATURE.md for full details and setup instructions.

• Tactical Units Tracking (experimental): Live tactical unit markers (aircraft, helicopter, ground, ship) on the map with real-time updates. Marker popups include "Last seen" timestamps and refresh snippets with speed/altitude. A "Live Units Only" filter (shows units seen in the last 10s) is synchronized between the list and the map. See docs/EN/features/TACTICAL_UNITS_TRACKING.md and scripts/DCS-SCRIPTS-FOLDER-Experimental/README_ENTITY_TRACKING.md for setup and details.

• MapDatabaseTools (Python): A collection of Python utilities for receiving, decrypting (AES-GCM), and visualizing DCS flight telemetry. Includes a PySide6 GUI with an embedded OpenStreetMap/Leaflet map for live aircraft tracking, a marker database, and helper scripts to manage map assets. See scripts/MapDatabaseTools/README.md for usage and configuration.

• Supported maps (marker DB):

Planned features and long-term improvements are tracked in the Roadmap document.

The GUI installer now automatically installs Export.lua to your DCS Scripts folder during the setup wizard.

Features:

• Auto-detection of DCS Saved Games folder
• Version detection - Shows current and new version
• Backup creation - Automatically backs up existing Export.lua
• Version comparison - Prompts before overwriting if Export.lua already exists
• Optional skip - Can skip installation if you prefer manual installation

Manual Installation (Alternative):

If you prefer to install manually or skipped the wizard step:

1. Copy Export.lua from scripts/DCS-SCRIPTS-FOLDER-Experimental
2. Paste into your DCS Scripts folder: %USERPROFILE%\Saved Games\DCS\Scripts\

This script enables DCS to write entity batches and player telemetry files into a subfolder that the Python forwarder reads.

After installation (automatic or manual):

• Start or reload your mission, or
• Restart DCS

to activate the export script.

The Python forwarder (DataPad Server) requires a local Python installation.

• On Windows, installing Python via the Microsoft Store (Python 3.12+) is recommended for simplicity.

• The GUI installer (run_installer.bat) automatically:

  • Creates a virtual environment (venv) if not present
  • Installs all required Python packages into that environment
  • Detects your DCS installation and Saved Games folder
  • Configures network settings and firewall rules (optional) This keeps dependencies isolated and clean.

• To update packages: re-run run_installer.bat

• To remove everything: delete the created venv folder

1. Navigate to the folder: /scripts/DCS-SCRIPTS-FOLDER-Experimental

2. Start the GUI installer – double-click: run_installer.bat → The GUI will automatically install dependencies and open the installer window (first run takes 1–2 minutes to install packages)

Server first installation Wizard

3. First-Time Setup Wizard (appears on first run):

   • The wizard will guide you through:
     • DCS Installation Detection – Auto-detects your DCS installation
     • Export.lua Installation – Automatically copies Export.lua to DCS Scripts folder with version detection
     • Dependency Installation – Installs required Python packages
     • Server Configuration – Configure network settings (bind IP, ports, etc.)
     • Firewall Setup (optional) – Add Windows Firewall rules for server ports

4. After setup is complete, the main installer window opens with tabs:

   • Dashboard – Server status and control (Start/Stop server)
   • Device Management – Manage authorized devices and generate QR codes
   • Server Configuration – Network and security settings
   • Installation Settings – DCS paths and file locations
   • Health Checks – System diagnostics and firewall configuration
   • Logs – Real-time server log viewer

Server health window

Server settings window

1. Open the Server Configuration tab

2. Configure the following settings:

   • Bind IP – IP address of the PC where DCS is running (Example: 192.168.1.100)
   • Target IP – Android devices in your Wi-Fi network (Example: 192.168.1.255 for broadcast, or 192.168.1.* for all devices in subnet)
   • Data Port – UDP port for telemetry data (default: 5010)
   • Handshake Port – UDP port for device handshakes (default: 5011)
   • Update Interval – How often to send data (default: 100 ms)
   • Enable Proof-of-Work (PoW) – Recommended for security (default: disabled)
   • PoW Difficulty – Difficulty level (default: 16 bits)

3. Click "Save Configuration"

• Server Bind IP → IP address of the PC where DCS is running
• Target IPs → Android devices (tablet or smartphone) in your Wi-Fi network
• You can:
  • Enter specific IPs individually, or
  • Use broadcast: 192.168.1.255, or
  • Use wildcard pattern: 192.168.1.* to target all devices in the subnet

1. Go to the Dashboard tab
2. Click "Start Server" button
3. Server status will show "● Server Running" (green) when active
4. The Logs tab shows real-time server output

Tip: You can minimize the GUI to system tray – the server continues running in the background.

Datapad device list and qr-code registration

The GUI provides an easy way to register devices via QR code:

1. Start the server from the Dashboard tab (if not already running)
2. Go to the Device Management tab
3. Click "Generate Token" button
   • If server is not running, you'll be prompted to start it
   • The GUI generates a secure registration token valid for 10 minutes
4. A dialog appears showing:
   • QR Code – Scan this with your Android app
   • Token Details – Server IP, port, expiration time
   • Registration Status – Shows when a device successfully registers

Datapad QR-code registration

5. The GUI automatically detects when your device scans the QR code and registers

   • Registration confirmation appears in the dialog
   • The device is automatically added to the authorized devices list
   • No server restart needed – registration happens in real-time

6. (Optional) You can manually add devices by clicking "Add Device" and entering:

   • Device Name
   • Device ID
   • Public Key (Base64)

If QR-code registration fails, try the checks below (quick and common fixes):

• Check Android app network permissions: ensure the app has the INTERNET permission and is allowed to use networks (no restrictive work profile or denied network access).

• Check Android firewall / antivirus / VPN: some devices ship with an app firewall or VPN that blocks UDP traffic; disable or allow the app temporarily and retry.

• Ensure both devices are on the same Wi‑Fi: your phone/tablet must be on the same local network (same subnet) as the server – mobile data or a different Wi‑Fi will not reach a local server.

• Verify the Server IP is correct: confirm the server IP shown in the QR code matches the server bind IP (and that the server is running on that interface).

• Verify the Handshake / Registration port: make sure the port in the QR payload (e.g., 5011) matches the server handshake port and any firewall rules on the server/PC allow incoming UDP on that port.

• Confirm the server is running and listening: check the server logs for "Listening for handshakes on" and ensure it reports the expected IP:port.

• Check token validity: registration tokens are time-limited and single-use — regenerate and try again if expired or already used.

• Look for specific errors: Example: sendto failed: EPERM on Android usually means the app is blocked from sending network packets (firewall, VPN, or missing permissions).

• Ask on GitHub Discussions: Prefer posting in the project's Discussions (https://github.com/arn-c0de/InteractiveChecklists/discussions) — include app logs (adb logcat) and server logs so we can reproduce and diagnose quickly.

• Or open a GitHub issue using the built-in template: Click New issue on the repo and select "QR Registration problem" — this pre-fills the required fields and helps us triage faster.

Activates the in App datapad functions

1. Open the Android app
2. Go to Settings → DataPad
3. Turn DataPad ON

Settings Menu for datapad

4. Open the DataPad Popup using the FAB button
5. Tap Settings in the DataPad Popup

Enter your Device Name

6. Enter a Device name

Enter your Server IP and Scan QR-Code

7. Scroll down set your ServerIP (recommend) then to QR-Code setup | or for Manual adding, copy Device Name, ID and Public Key and enter as new entry in authorized_devices.json
8. Tap Scan QR Code
9. Scan the QR code displayed on your PC screen
   • (First time only – securely registers your device)
10. Enable the toggle button in the DataPad Popup

• If the correct server is selected, a heartbeat is sent every 30 seconds

• When a DCS mission starts and you are seated in an aircraft, the forwarder (DataPad Server) begins sending live data to the app

• The current status is shown in the top info bar:

  • 🔴 Red – No incoming data / No mission running
  • 🟡 Yellow – Mission running, but not in an aircraft / No active live data
  • 🟢 Green – In an aircraft and receiving telemetry and/or tactical unit live data

Some DCS files may be blocked by Group Policy or antivirus software.
This can prevent correct operation.

1. Press the Windows key and type PowerShell
2. Right-click Windows PowerShell → Run as Administrator
3. To unblock a single file, enter:

Unblock-File "C:\Program Files\Eagle Dynamics\DCS World\bin\lua-dxgui.dll"

4. Press Enter

Get-ChildItem "C:\Program Files\Eagle Dynamics\DCS World\bin\*.dll" | Unblock-File

Press Enter.

If unblocking does not help:

1. Open DCS Launcher
2. Go to Settings (gear icon)
3. Click Repair
4. Wait for the process to complete

This will restore and unblock all affected files.

Server main window

7. After successful registration, switch to the Device Management → Devices tab

   • Your newly registered device now appears in the device list
   • The device status is shown as Authorized / Connected

8. Go back to the Dashboard tab

9. Click "Start Server" to finalize and run the server

   • The server now starts with the registered device active
   • Live connections are accepted immediately

✅ Done! The app should now receive live telemetry and tactical data from DCS.

• Connection is encrypted (AES-256 + ECDH handshake) – similar to secure websites
• Only registered devices can connect (via QR code or manual list)
• First connection is remembered (Trust on First Use) → protects against fake servers later
• Optional extra protection: Proof-of-Work (anti-spam) – can be enabled in the GUI's Server Configuration tab

For most users the QR code method is secure enough and very simple.

The GUI installer is Windows-only. For Linux/macOS or if you prefer command-line control:

Note: The Windows TUI (Text-based menu with install.bat/run.bat) has been replaced by the GUI installer in version 1.0.25+. For the legacy TUI, use branch 1.0.24.

Manual command-line start (all platforms)

cd scripts/DCS-SCRIPTS-FOLDER-Experimental
python -m venv venv
source venv/bin/activate          # Linux/macOS
# or on Windows: venv\Scripts\activate
pip install -r requirements.txt
python forward_parsed_udp.py --authorized-devices authorized_devices.json --host YOUR_PC_IP --port 5010 --skip-qr-prompt

Important: Use --skip-qr-prompt to disable the interactive QR prompt when starting the server. The GUI generates tokens separately.

Entity Contacts (tactical units): Enable Entity Tracking and run the forwarder with entity tracking enabled to receive live markers; see scripts/DCS-SCRIPTS-FOLDER-Experimental/README_ENTITY_TRACKING.md and docs/EN/features/TACTICAL_UNITS_TRACKING.md.

See docs/EN/features/DATAPAD_FEATURE.md for full usage, configuration, and troubleshooting.

Phase 1 (experimental): This is Phase 1 of DataPad — future phases will add more telemetry, visualizations, and security improvements.

Next up: 2-way communication (experimental) to enable data flow back to DCS.

File explorer showing the hierarchical file and folder structure

Interactive Markdown checklist with stateful checkboxes

PDF viewer with drawing, highlighting and annotation capabilities

QuickNotes editor with markdown support and autosave

Landing pattern calculator displaying flight path calculations

Early ATC features showing airspace visualization

AA range rings visualization

Live tactical markers displaying real-time unit positions

Flight path tracking overlay on the aviation map

Route planning with labeled waypoints and flight paths

Route planner interface with live preview

Landing route creation sheet with configuration options

DataPad displaying live aircraft telemetry from DCS World

Application settings and configuration panel

📝 NOTE
This is a test recording to evaluate recording performance, tablet capture workflow, resolution settings, and overall system stability during DCS gameplay. Mission content and pacing are deliberately simple and functional.

Step-by-step instructions to get the project running locally.

1. Prerequisites

   • Install Android Studio (Arctic Fox or later recommended).
   • Install a compatible JDK (Java 11 or later recommended).
   • Configure Android SDK and at least one emulator or use a physical device.
   • For Python forwarder scripts (optional): install qrcode and cryptography dependencies: pip install qrcode[pil] cryptography cffi (use a virtual environment to avoid system conflicts).

2. Clone the repository

git clone https://github.com/arn-c0de/InteractiveChecklists.git
cd InteractiveChecklists

3. Build with Gradle (command-line)

./gradlew assembleDebug

4. Open in Android Studio
   • Open the InteractiveChecklists directory in Android Studio.
   • Let Gradle sync and allow Android Studio to download any missing SDK components.
   • Run the app on an emulator or connected device.

• Supported OS: Windows, macOS, Linux (for development).
• Android Studio: Arctic Fox or newer recommended.
• JDK: Java 11+ recommended.
• Android SDK: API level corresponding to the project's compileSdk and targetSdk (see build.gradle.kts).

• From Android Studio: Open the project, wait for Gradle to finish syncing, then select a target device and click Run.
• From the command line: ./gradlew assembleDebug builds an APK; use ./gradlew installDebug to install on a connected device.

We welcome contributions. For guidelines, issue workflow, and coding standards, see COLLABORATORS.md.

All contributions are currently unpaid and voluntary. This is a non-commercial project without donation functionality or sponsorship options at this time.

Quick contribution ideas:

• Improve documentation or add examples.
• Add or extend tests.
• Fix small UI/UX bugs or accessibility issues.

For larger or breaking changes, please open an issue first to discuss design and scope.

If you encounter issues or have questions:

• Open an issue in this repository.
• For security-sensitive issues, please follow the instructions in SECURITY.md.
• For contribution coordination and discussions, see COLLABORATORS.md.

When reporting a bug, please include a screenshot if possible.
Use the screenshot to mark or highlight the exact area where the issue occurs, and briefly describe what is shown and what is wrong in that location.

• Q: How do I run tests?
  • A: There are unit tests under app/src/test. Run them via ./gradlew test.
• Q: What is the license?
  • A: This project is licensed under CC-BY-NC-SA 4.0. See the LICENSE file for details.
• Q: Where is the documentation?
  • A: See the docs/ folder or the Documentation index.

Thanks to all contributors and to the Jetpack Compose and Android open-source ecosystems used in this project.

This project is licensed under the terms in the LICENSE file (CC BY-NC-SA 4.0).

---

App Version: v1.0.25 Last Updated: 2026-01-18