Dcspy

Latest version: v3.6.3

Safety actively analyzes 710445 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 9

1.0.0

Not secure
* **Ka-50 Black Shark** data from PVI-800 shows (in similar boxes) on LCD
* ProtocolParser for DCS-BIOS has a new optimized state machine
* LCD SDK is re-written from scratch:
* low and high-level API
* auto-loading C library during importing
* all API is type annotated and well documented
* move loading LCD C-library from G13 handler
* internal:
* refactoring and rename internals of G13 handler module
* add unit tests

0.9.2

Not secure
* LCD prints current waiting time to connect to DCS
* when DCS exits from plane/mission exception is catch and handle correctly
* lots of internal changes, preparing for new features, most important:
* change structure of AircraftHandler, move subscription to DCS-BIOS changes out of planes
* update and clear methods move from G13 handler to LCD SDK

0.9.1

Not secure
* G13 handler have display property to send text to LCD
* rename starting script to dcspy.exe
* starting script shows now waiting time for DCS connection
* minor code optimization and refactoring

0.9.0

Not secure
* based on version [specelUFC v1.12.1](https://github.com/specel/specelUFC/releases/tag/v1.12.1)
* added basic handling for Ka-50 PVI-800 data is received but not formatted properly
* F-16C DED should work, but not four buttons under LCD - I don't have it, so it is hard to test
* G13-handler detects 32/64 bit of Python and loads a correct version of LCD Logitech C-library
* adding basic logging for debugging - prints on console
* all defined aircraft are detected and loaded on-the-fly during operation
* defines new plane should be easy, use AircraftHandler as base class
* Python LCD SDK was cleanup
* other refactorings and code duplication removal

Page 9 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.