Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Increase Keyboard Brightness" key overrides tachyon mode stability cap #278

Open
Duckleeng opened this issue Apr 8, 2024 · 2 comments
Open
Labels
bug Something isn't working

Comments

@Duckleeng
Copy link

Describe the bug
When tachyon stability cap is in the locked state, using the "Increase Keyboard Brightness" special character will override it and unlock the stability cap. The brightness will go to 100% if the key is held for long enough.

To Reproduce
Steps to reproduce the behavior:

  1. Turn on (lock) the tachyon stability cap
  2. Hold the "Increase Keyboard Brightness" special character
  3. Refresh the Wootility webpage
  4. Brightness has now exceeded the stability cap

Screenshots / Video
image
image

Desktop

  • OS: Windows 11
  • Motherboard: MSI PRO Z790-A

Wootility and Firmware version
Web Wootility v4.6.16
Firmware 2.7.2

Keyboard Type
Wooting 60HE ARM

@Duckleeng Duckleeng added the bug Something isn't working label Apr 8, 2024
@Duckleeng
Copy link
Author

Duckleeng commented May 16, 2024

This issue seems to have been partially addressed in the latest firmware update, the behavior of using the RGB keys is now quite buggy though:

  • After unlocking the tachyon mode stability cap, putting the brightness to 100%, then lowering the brightness via the Decrease Brightness Key to 0, the Increase Brightness key acts as if the stability cap is locked again and won't raise the brightness above 70%
  • After increasing the brightness from 0 to 70 via the Increase brightness key, Wootility reports (seemingly) random brightness values from 60-70 (after a refresh of the website), even though the actual physical brightness is at 70%

@Duckleeng
Copy link
Author

Disconnecting and reconnecting the keyboard also seems to set the brightness to 0%, instead of the value it was previously at.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Inbox
Development

No branches or pull requests

1 participant