Hi! I've been using flydigictl with a Vader 3 Pro ONE PIECE on Fedora and built on your great work. I have ready:
- Fixes (some with unit tests — the project's first): a build break on master, state packets being randomly misparsed as config data (intermittent read/write corruption), the
254 Space Station marker being lost on every write, a LED-mode panic, a stale-connection bug in the daemon, and a SELinux issue in make install on Fedora
- Button mapping command (
flydigictl mapping): remap buttons stored on the controller, turbo, hide buttons from games
- Keyboard mapping through uinput: buttons can type keyboard keys on Linux, like Space Station does on Windows (input stream format from the SDL HIDAPI Flydigi driver)
- Qt GUI (PySide6, thin shell over the CLI) and packaging skeletons for the major distro families
Everything is split into small, independently reviewable PRs which I'd like to send one at a time, starting with the fixes. Branches are ready on my fork. Are you interested? Anything you'd like done differently?
Hi! I've been using flydigictl with a Vader 3 Pro ONE PIECE on Fedora and built on your great work. I have ready:
254Space Station marker being lost on every write, a LED-mode panic, a stale-connection bug in the daemon, and a SELinux issue inmake installon Fedoraflydigictl mapping): remap buttons stored on the controller, turbo, hide buttons from gamesEverything is split into small, independently reviewable PRs which I'd like to send one at a time, starting with the fixes. Branches are ready on my fork. Are you interested? Anything you'd like done differently?