Razer Huntsman V3 Pro 8KHz - When switching profiles on this keyboard, the profiles can sometimes get copied into each other.
The issue occurs in both the Retail and Beta versions of Synapse.
Example:
- I have a profile called “Default”, which I use in Windows. Actuation is set to 2 mm for all keys in this profile.
- I have a second profile called “FPS”, which I use for games (for example, Overwatch). Profile switching is handled automatically by Synapse, and the profile is linked to the game. Different Actuation values are configured for different keys in this profile, and Rapid Trigger is also enabled for some keys.
- When I have a game running and, during that time, I ALT+TAB to Windows and then return to the game, it sometimes happens that the settings of one profile are copied into the other profile.
- The copying can happen in both directions: Default → FPS or FPS → Default.
What I have observed:
- In Synapse, it takes a little while for the profile to switch on this keyboard.
- This is clearly visible, for example, in the Actuation setting. When switching profiles, it looks like this: the current value is set to 2 mm and I switch to a profile where it should change to 3 mm. During the switch, the Actuation value changes as follows: 2 mm > switch to another profile > for a short time it changes to 1.2 mm (this is the keyboard's default setting) > 3 mm.
- It seems quite likely that when quickly ALT+TABbing to Windows and then back to the game, another profile change may occur while the previous profile switch is still in progress. The profiles may then somehow become combined with the profile that Synapse was originally switching to, causing the values to be overwritten.
This is a very unpleasant bug that makes it impossible to fully use the potential of both the keyboard and its accompanying software.
Note: After many years of using Synapse (including previous versions), I have to say that Synapse has always had problems with activating and switching profiles linked to the .exe files of games/programs. This was especially noticeable with ALT+TAB, which after some time could completely “confuse” Synapse to the point where the issue could not be resolved in any other way than by restarting Synapse.