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

Basilisk V3 cannot enable underneath LEDs if turned off in Windows #609

Closed
kathampy opened this issue Mar 29, 2022 · 6 comments · Fixed by #606
Closed

Basilisk V3 cannot enable underneath LEDs if turned off in Windows #609

kathampy opened this issue Mar 29, 2022 · 6 comments · Fixed by #606
Labels
Support Device is visible but XY is not working correctly

Comments

@kathampy
Copy link

kathampy commented Mar 29, 2022

The Basilisk V3 has a layer of LEDs under the mouse.

Razer macOS can control LEDs only in the default / 1st on-board memory profile.

I have a macOS profile with custom macros which I activate in Windows before plugging the mouse into macOS, so that Synapse 3 copies the profile into the 1st on-board memory profile. This profile also has brightness disabled because I want this to be the default in macOS unless I specifically set a color effect.

Razer macOS allows me to enable the brightness only for the scroll wheel and logo. There is no way to enable the brightness for the LEDs under the mouse. If the brightness is already enabled in Windows, Razer macOS can control the colour of bottom LEDs.

@WrathofthePast
Copy link
Collaborator

Change it to the white profile after plugging into macOS. The white profile is the last state, so it keeps all the Synapse 3 settings while allowing razer-macos to control the mouse.

@kathampy
Copy link
Author

kathampy commented Mar 29, 2022

Change it to the white profile after plugging into macOS. The white profile is the last state, so it keeps all the Synapse 3 settings while allowing razer-macos to control the mouse.

I already do that. The underglow LEDs do not turn on when changing the brightness in macOS if they were already off. Only the scroll wheel and logo LEDs turn on.

@WrathofthePast
Copy link
Collaborator

Change it to the white profile after plugging into macOS. The white profile is the last state, so it keeps all the Synapse 3 settings while allowing razer-macos to control the mouse.

I already do that. The underglow LEDs do not turn on when changing the brightness if they were already off.

I audited the Basilisk V3 Support... I found an error, but it's unclear whether that is the cause of this particular issue. I created two PRs, #606 and 1kc/librazermacos#32, to fix it.

@WrathofthePast WrathofthePast added the Support Device is visible but XY is not working correctly label Mar 29, 2022
@WrathofthePast WrathofthePast linked a pull request Mar 29, 2022 that will close this issue
@kathampy
Copy link
Author

kathampy commented Mar 29, 2022

The menu items under Razer Basilisk V3 > Brightness are only Logo and Scroll. Shouldn't there be a third option for the other LEDs? There is probably a similar issue for the Basilisk Ultimate.

@WrathofthePast
Copy link
Collaborator

The menu items under Razer Basilisk V3 > Brightness are only Logo and Scroll. Shouldn't there be a third option for the other LEDs? There is probably a similar issue for the Basilisk Ultimate.

Excellent catch. The whole implantation is screwed up. Matrix brightness is disabled and missing from the backend. I added it to the existing PRs. This is the fourth error I've found with the Basilisk V3 now (I caught & fixed one relating to the DPI before v0.4.9 released). These PRs will certainly fix this issue.

@WrathofthePast
Copy link
Collaborator

The menu items under Razer Basilisk V3 > Brightness are only Logo and Scroll. Shouldn't there be a third option for the other LEDs? There is probably a similar issue for the Basilisk Ultimate.

Excellent catch. The whole implantation is screwed up. Matrix brightness is disabled and missing from the backend. I added it to the existing PRs. This is the fourth error I've found with the Basilisk V3 now (I caught & fixed one relating to the DPI before v0.4.9 released). These PRs will certainly fix this issue.

The PR was merged on the backend. The frontend PR will be merged with the next release.

@1kc 1kc closed this as completed in #606 Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Support Device is visible but XY is not working correctly
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants