Issue: Huntsman V2 TKL (DE Layout) - Synapse Key Recording Fails for Modifier Combinations

Hi everyone,

I recently purchased a Razer Huntsman V2 TKL with a German (DE) layout and I'm running a German version of Windows 11. I'm encountering an issue when trying to bind a key to the combination "Shift + Ctrl" using the "Key Recording" feature in Razer Synapse. While I've seen other threads suggesting this should be possible, it's not working for me.

Here's what happens when I attempt the "Shift + Ctrl" binding:

1. Pressing Shift, then Ctrl:

   • While both keys are held down, the Synapse binding box shows: "Shift + Ctrl + STRG" (STRG being the German equivalent of Ctrl).
   • Upon releasing the keys (regardless of the release order), only "STRG" remains in the box.

2. Pressing Ctrl, then Shift:

   • While both keys are held down, the Synapse binding box shows: "Shift + Ctrl + UMSCHALT" (UMSCHALT being the German equivalent of Shift).
   • Upon releasing the keys (regardless of the release order), only "UMSCHALT" remains in the box.

Essentially, I cannot get both Shift and Ctrl to remain bound together; only one of their German equivalents stays. I've also tried using a macro to ensure precise timing for the key presses and releases, but this doesn't resolve the issue. The behavior within the macro recording reflects the observations above.

Further Observations on Modifier Key Behavior in "Key Recording":

• Single Standard Modifiers (Ctrl, Shift, Alt): When I press and hold a single standard modifier like Ctrl, the box initially shows "Ctrl + STRG". After release, "STRG" correctly remains. This pattern is consistent for other similar modifiers (e.g., Shift shows "Shift + UMSCHALT" then UMSCHALT).
• Caps Lock ("FESTSTELL"): This key behaves differently regarding its initial display and in combinations, depending on the order pressed:
  • When I press and hold Caps Lock alone, the box immediately shows "FESTSTELL" (the German term for Caps Lock) without displaying the English "Caps Lock" alongside it.
  • When combining with another modifier (e.g., Ctrl/"STRG"):
    • If Caps Lock ("FESTSTELL") is pressed last (e.g., holding Ctrl then pressing Caps Lock), the combination generally records correctly (e.g., "STRG + FESTSTELL" or similar appears and remains).
    • However, if the other standard modifier is pressed last (e.g., holding Caps Lock then pressing Ctrl), the German name of that last-pressed standard modifier ("STRG" in this case) overwrites the entire expression, leaving only "STRG" in the box.

My Hypothesis:

It seems that for "Key Recording," Synapse attempts to replace the English modifier names with their German equivalents. The core issue appears when multiple standard modifiers (like Shift, Ctrl, Alt) are involved, or when a standard modifier is pressed after another key like Caps Lock.

• When two standard modifiers are pressed, the software identifies the initial combination (e.g., "Shift + Ctrl") but then seems to only successfully substitute one of them with its German counterpart in the final binding.
• The Caps Lock behavior reinforces this: "FESTSTELL" is recognized directly. If it's pressed last, it seems to bypass the faulty logic. But if a standard modifier (like "STRG") is pressed after "FESTSTELL," its problematic German name substitution logic appears to take precedence and overwrites the previously established "FESTSTELL."

This suggests a potential bug in how Synapse handles the priority and replacement of localized German modifier names when multiple keys are part of a "Key Recording," especially concerning the last standard modifier pressed in a sequence.

Could this be the case? Has anyone else experienced this specific order-dependent behavior or found a solution? Any insights or assistance would be greatly appreciated.

Greetings,

GoldenPoppystoryleet161