Synapse 3 rejects macro keybinding for a Naga X

Found a way around this issue. I downloaded the prior Naga Trinity Profiles from the Cloud and although Synapse 3 would assign the Macros correctly to the ill behaved Trinity, it would not accept any attempt to bind those Macros to the Naga X buttons. By duplicating / renaming each Macro these new versions would then bind successfully. Not a pain free upgrade experience but the job got done.

I stand corrected on finding a solution. Came back later to finish the binding and what had stuck was now broken. Created a new profile and a Macro from scratch and attempted to assign it to a side button Synapse 3 responded with " This mapping requires Synapse " Now is it possible this refers to the earlier version of Synapse. The reason I installed 3 is because the earlier version would not recognize Naga X and your documentation for Synapse 3 claims to support Naga X. Given that I am in rural Colorado and the drive to the nearest BestBuy was 146 miles round trip and that before I picked up the Naga X I held a Corsair 16 button mouse in my hands and wondered if I should switch brands, I expect some indication of support or else I'll be taking another 3 hr drive over mountain roads. And will also return the Kraken I bought which sounds nowhere as good as the 10yr old Logitech G430 it was to replace.

I replied to your other thread. Were you able to reset your mouse through the Razer Synapse 3.0 settings? Please replicate the issue by logging in as a guest user account. Feel free to send me a PM should you need additional assistance.