[Feature] Hypershift chroma profile | Razer Insider
Skip to main content

[Feature] Hypershift chroma profile

  • October 13, 2023
  • 1 reply
  • 159 views

I want to be able to change the lightning when holding the hypershift key. I chose to write it in a scrum user story to make it easily understandable what the specific actions I want to be able to do. I only have a keyboard but I dont see why this wouldn't apply to mouses too.

I think this feature has been requested before but not in the beta so I thought might aswell post it here too.

 

User story: A user wants to be able to change the lightning profile that shows on the keyboard when holding down the function key to easily see what keys has a hypershift action bound to it. Said profile should be easily customizable by the user in the chroma software. Diffrent colors can be assigned to each button to indicate to the user a diffrent action.

Acceptance Criteria:

  • All keys with a hypershift action bound to them should be clearly highlighted in the chosen lighting profile as default.
  • When the user holds down the function key, the keyboard should display the specified lighting profile.
  • The user should be able to customize the lighting profile in the Chroma software.
  • The Chroma software should provide an intuitive and user-friendly interface for editing the hypershift lighting profile.
  • The user should be able to change the colors of individual keys to indicate different actions.
  • Any changes made in the Chroma software should be reflected in real-time on the keyboard's lighting profile.
  • The selected lighting profile should persist across reboots and device connections (when synapse is running).
  • Ensure that the feature does not significantly impact the keyboard's performance or responsiveness.

1 Reply

  • Insider Mini
  • November 4, 2023

YES PLEASE. This would make a world of difference when using macros stored in Hypershift.

I’m currently proxying this functionality by bounding chroma profile switching (which I manage and maintain manually...) as a guite to which keys have what macro bound to them before I press `fn`… Less than optimal but better than the alternative...