OpenTabletDriver 0.6.7

What's new in 0.6.7

OpenTabletDriver v0.6.7 releases after over a half of year of development! Over 300 issues and pull requests was targeted for this milestone, making it the biggest single milestone, surpassing even v0.6.0. While a lot of the changes for this version has been for code quality and maintainability, this version still contains some notable changes.
We hope that you enjoy this feature release of OpenTabletDriver!
Notable Features/Bugs Fixed
Wheel Support (#3497) by @Mrcubix and @joha4270
(and multi-wheel support in #4483 by @gonX)
You can now use the tablet pad wheel and roller for many tablets.
Mrcubix backported and completed the effort by @joha4270 in #2669 to the 0.6.x branch
Please see the TABLETS.md file for this release to determine if your tablet is fully supported yet.
Mouse Scroll Bindings (#3840) by @Mrcubix
Mouse-based output modes (ie. not Linux Artist Mode and not Windows Ink) can now use arbitrary bindings to scroll as if a scroll wheel was being scrolled.
Reworked Tablet Debugger (#4434) by @gonX
Note: The data recording feature has been moved away from the main window, into an option in the menu.
New features:
- Filtering by:
- Tablet Model
- Report Parser source type
- Binary decoding option for raw data in addition to the existing hexadecimal decoding
- All implemented report-related interfaces now add additional statistics
- Full ranges for range-based values (position, pressure, tilt, etc)
- Button state transition verification
- Data recording now also annotates these additional statistics
Tablet debugger recordings will likely be mandatory for future tablet configuration additions and changes to verify full feature compatibility.
Silence update notifications (#4270) by @Kuuuube
Simply add --skipupdate to the GUI's launch options to disable the updater.
Meta Quest link conflict solved (#4476) by @fredemmott
Implemented a workaround for a long-standing issue with newer Meta Quest firmware bugs that would cause the VR headset to not link properly as long as OpenTabletDriver was running. See issue #3696 for details.
Better binding errors when bindings are unsupported (#4738) by @gonX
The built-in bindings used to be able to be configured with any output mode and the user would not have a chance to know that their binding would not work (e.g. mouse scrolling on the output modes "Windows Ink" and "Linux Artist Mode") other than it just silently dropping its input. …

Full release notes »