Wootility v4.3

Hi everyone, welcome to Wootility v4.3!

We're back on the Wootility development train. We've been working on this update for a while, but the 60HE launch put it on hold. Now that that's done we're back in full force on the Wootility.

In this update, we're bringing some much-needed love to DKS and we're expanding our support for the Classic (previously Legacy) Controller.

We're also trying out a new style of patch notes, with more background, explanation pictures and examples how you can use the new features. Please let us know what you think. (If you want to read it another time, there's a new "Read latest patch notes" button in the settings.)

Just wanted to say a big thank you to everyone who helped with reporting issues, providing feedback and testing out alpha / special builds (#rocket_league). Most of our bug fixes come directly from https://github.com/WootingKb/wootility-issues/issues. Go check it out and help us find new issues or add additional feedback to existing issues.

P.S. The primary goal of the next significant update v4.4 is Flaretech compatibility, i.e. Wooting One and Wooting Two support, bringing Wootility v3 users up to Wootility v4!

Highlights

DKS Improvements

• You can now bind every Remap binding onto DKS, including Gamepad Mappings!
  • Note: Analog bindings e.g. Left joystick will always be active across the entire press.
• Added the option to configure the actuation point of the "Start of the key press" and "Release of the key" actions.

• It's now possible to have multiple key active ranges over the press, where the key is deactivated then reactivated again. See A key in example picture below.

• Many issues with DKS fixed, e.g. #115 #113 #4 #3
• There is a new advanced setting called "Tick rate" which allows you to control how long key presses in DKS need to be held/released. This ensures that games with tick-based input handling (e.g. Minecraft) are able to correctly see every key event.
• You can now edit DKS of inactive profiles.

As a note, with this DKS update there were some subtle changes to how DKS items are configured internally and as such some conversions were needed to be added to automatically update existing bindings to behave the same in the new version. This should all be handled for you, except for one case, the configuration you can see below, commonly referred to as "Budget trigger" (due to its previous behaviour exihibiting rapid trigger like benefits before rapid trigger was a full feature)