Razer Synapse Beta Macro Problem. | Razer Insider
Skip to main content
Question

Razer Synapse Beta Macro Problem.

  • 31 May 2024
  • 2 replies
  • 143 views

In the newer program Razer Synapse Beta, a reoccurring problem is in the “macro” side of things.

I have used the Razer Synapse 3 macro stuff, no problem, and at some point, some Razer program wasn’t working for a while no matter what I did, so I clean re-installed Razer Cortex (which works fine, might I add), and Razer Synapse. Of course, I saw the “NEW!” Razer Synapse and decided to install that instead of Razer Synapse 3. I was in love with everything new and how much faster and nicer it was. It all changed when macros came into play. I re-installed the Macro module and imported my macros, checking all four of them for any corruption or bugs. Every macro was exactly how I wanted. For simplicity in the rest of this discussion, we’ll focus on “Macro 1.” (I didn’t know that you could rename them back then. (Okay, this was like a week ago, nevermind.)) Macro 1 was a 23 CPS Left Click Macro, with 0.02 second delay between each click or release. In Razer Synapse 3, this macro had no problem, executing perfectly. This macro was bind to Mouse Button 4, at the “Play while assigned key is pressed” state. Anyway, when executing the macro, it was kind of working, but when I released Mouse Button 4, it stopped in the middle of the macro, in this case still holding down the left click. When I pressed the regular left click button again, it went back to normal.

I went back to Razer Synapse 3, but this is a bug you should look in to. If stopping in the middle of the play-back macro is intentional, I recommend re-thinking that choice, or making a setting toggleable between “Stop at Exact Position” or “Finish Macro Before Stop.”

2 Replies

May I add, the device I am using is the Razer Basilisk V3 (not the pro version.)

May I add, the device I am using is the Razer Basilisk V3 (not the pro version.)

trying to get any help on here is like getting teeth pulled, they just dont help us.

this seems to be a change in the new version, as well as being completely unable to HOLD a keystoke button down, because when the marco ends, it releases the keyboard key even without the command to do so.

this is also something that the last version of synapse didnt do, and I was previously able to have a “play once” macro be able to hold down any keyboard stroke.

Reply