DCSpy
DCSpy is able to pull information from DCS aircraft and display on Logitech G-series keyboards LCD.
Features:
- Logitech device with 160x43 px four (4) lines monochrome LCD - G13, G15 (v1 and v2) and G510
- Logitech device with 320x240 px eight (8) lines full RGBA LCD - G19
- Support for other Logitech devices:
- Keyboards: G910, G710, G110, G105, G103, G11
- Headphones: G35, G633, G930, G933
- Mouses: G600, G300, G400, G700, G9, MX518, G402, G502, G602
- Setup G-Keys to any toggle, switch or knob in cockpit - Setup of G-Keys
- Support for all aircraft (official and mods) with clickable cockpits - DCS-BIOS aircraft
- Modern looking GUI using Qt6/PySide6
See more information on documentation page.
Aircraft and instruments
There are to kinds of supported aircraft:
- Basic - allow assigning all G-Keys of Logitech keyboard to aircraft's instruments in the cockpit (all clickable cockpits supported by DCS-BIOS)
- Advanced - additionally can display some information on LCD (listed below)
Why a such way? Basically advanced support is for aircraft that I own and therefore can test it.
Advanced
- F/A-18C Hornet UFC - Up Front Controller
- F-16C Viper DED - Data Entry Display
- Ka-50 Black Shark II / III - PVI-800 and autopilot channels
- Mi-8MTV2 Hip - autopilot channels and Radio information
- Mi-24P Hind - Autopilot channels and modes and Radio information
- A-10C Warthog / A-10C II Tank Killer - Radio frequency information
- F-14A / F-14B Tomcat - basic support for RIO CAP
- AV-8B Night Attack Harrier - Up Front Controller and Option Display Unit
- AH-64D Apache - Enhanced Up Front Display (EUFD)
- F-15E Eagle - Upfront Control Panel
- F-4 Phantom II - UHF (ARC 164) Radio
- C-130J 30 Hercules - not yet decided (not ready in BIOS)
- more to come...
Requirements
- Logitech Gaming Software 9.04.49
- DCS-Skunkworks DCS-BIOS:
- DCS-BIOS 0.11.3 or newer (can be installed directly from DCSpy)
- However, it is recommended to use Live DCS-BIOS latest git version
- Git it is necessary to use the live version of DCS-BIOS
- DCS World: 2.9.25.21402, but any version from 2.9.* branch should be fine.
- optional:
- Python 3.14 but 3.10+ should be fine (see installation)
New ideas
I have lots of plans and new ideas how to improve it internally and form a user's perspective, but don't hesitate to contact me. Maybe it will motivate me to implement some new stuff. Please open issue if you find a bug or have any crazy idea. You are welcome dcspy discord server.
Contributing
You want to contribute, perfect see: contributing guide.
Credits
More details here.
1 maintainer
Metadata
1 maintainer
Release files for dcspy 3.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dcspy-3.8.1.tar.gz | 14.5 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dcspy-3.8.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.4 MB
Release files / dcspy-3.8.1.tar.gz
| Download URL | dcspy-3.8.1.tar.gz |
|---|---|
| Size | 14.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73cf36e9003e5696f3d8c66b3e6b46d26a3c135bf19f90b83bd4e6844b911c6b
|
|
BLAKE2b-256 checksum How to use checksums |
1b1f01e4038f3c6f899e5e2764a1a4a65ce8be628365973472c096fd20832b51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency logRelease files / dcspy-3.8.1-py3-none-any.whl
| Download URL | dcspy-3.8.1-py3-none-any.whl |
|---|---|
| Size | 14.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5519582ffda1d046fb1fd14460692fb762ce2adceed9b7ccaea55a524e18b97
|
|
BLAKE2b-256 checksum How to use checksums |
e48fa0c9e1ca3b9a4f5788196cf39bd75f41d248e18b115e0f89ecb0054db0c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency log
