Hello. This bug is fairly simple. I just got a Basilisk V3 Razer mouse, but when creating in the Chroma Studio, using Reactive at all simply entirely disables any mouse lights. It doesn’t matter what layer the Reactive effect is on, it seems to universally cause the lights on the mouse to stop working entirely. I was wondering if anybody has had any similar experiences or solutions to this issue. I have a Blackwidow keyboard as well, which works perfectly fine with the Reactive effect This seems to be the only effect that has this problem.
Solved
Chroma Lighting for Basilisk V3 bug regarding Reactive lighting in Chroma Studio
Best answer by polyOPALYellowRose589
Hello. This isn’t necessarily a fix, but you can use reactive on your keyboard without your mouse by putting the reactive effect in a new group/folder. It’ll work until the bug gets fixed, though I’m fairly certain it won’t help you get reactivity to work in chroma studio.
I’ve actually noticed the same thing. I have been trying to play around with it thinking maybe I broke something. The reactive layer seems to only have this impact when using the chroma connect. The reactive function seems to work just fine when you assign it to the Basilisk from the Synapse instead. I’m also using the Beta versions of the Chroma and Synapse apps but I’m unsure as to whether or not that makes a difference.
1 person likes this
Hello. This isn’t necessarily a fix, but you can use reactive on your keyboard without your mouse by putting the reactive effect in a new group/folder. It’ll work until the bug gets fixed, though I’m fairly certain it won’t help you get reactivity to work in chroma studio.
Unsure how to edit, but it does also solve the reactivity issue with the mouse.
Edit: Well, now I know how to edit and I can’t delete my reply.
had the same issue, while on the beta, putting another reactive in a separate group allows for the bug to be fixed, mine looks like this right now
Group 2
Reactive (mouse only)
Group 1
Reactive (All else)
Static
I have the reactive working on everything with this method
GallowsCallibrator wrote:
had the same issue, while on the beta, putting another reactive in a separate group allows for the bug to be fixed, mine looks like this right now
Group 2
Reactive (mouse only)
Group 1
Reactive (All else)
Static
I have the reactive working on everything with this method
GallowsCallibrator you are an absolutely beautiful summabish. I owe you.
GallowsCallibrator wrote:
had the same issue, while on the beta, putting another reactive in a separate group allows for the bug to be fixed, mine looks like this right now
Group 2
Reactive (mouse only)
Group 1
Reactive (All else)
Static
I have the reactive working on everything with this method
To add to this, I discovered that just putting Reactive (Mouse and all else together) in a folder, fixes this issue too.
Reply
Sign up
Already have an account? Login
Log in with Razer ID to create new threads and earn badges.
LOG INEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.