Basilisk Mobile; On-board Memory/Local Profile cannot use AI button, despite being remapped. | Razer Insider
Skip to main content

Basilisk Mobile; On-board Memory/Local Profile cannot use AI button, despite being remapped.


The new Razer Basilisk Mobile, when synapse is closed and the button remapped, cannot use its AI button at all for any given purpose on the normal layer. Hypershift, however, does properly register its remapped function. 

 

For example, if Mouse Button 4 were remapped as Hypershift, the AI button remapped to Mouse Button 4, and on the Hypershift layer, a function such as ‘Lower Sensitivity Stage’ were selected, once Synapse is closed the Hypershift would remain, the AI button(which is now Mouse Button 4) would not work, and the Lower Sensitivity Stage would also work when Hypershift is depressed. 

As I do not use the AI functionality, and on a laptop I would rather save as much memory as possible, closing the 400 MB process that is Synapse would be appreciated while I use my mouse to do other things.

 

 

Did this topic help you find an answer to your question?

0 Replies

Be the first to reply!

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings