Huntsman Elite, issues with Ctrl + Shift + F | Razer Insider

Huntsman Elite, issues with Ctrl + Shift + F

  • 14 November 2018
  • 3 replies
  • 8 views

I bought the keyboard in hopes of using it for my personal programming.

When in an IDE (Visual Studio 2017 or Jetbrains Rider), I cannot seem to press Ctrl + Shift + F.

I found an online keyboard debugger (https://codepen.io/QDeltaE/pen/PjXWZr)
and I've been playing around with it. Here are my logs in testing:

Ctrl + F:
>Keydown ↓ Key: "Control" KeyCode: 17
>Keydown ↓ Key: "f" KeyCode: 70
>Keyup ↑ Key: "f" KeyCode: 70
>Keyup ↑ Key: "Control" KeyCode: 17

Shift + F:
>Keydown ↓ Key: "Shift" KeyCode: 16
>Keydown ↓ Key: "F" KeyCode: 70
>Keyup ↑ Key: "F" KeyCode: 70
>Keyup ↑ Key: "Shift" KeyCode: 16

Ctrl + Shift + F
>Keydown ↓ Key: "Control" KeyCode: 17
>Keydown ↓ Key: "Shift" KeyCode: 16
>Keyup ↑ Key: "F" KeyCode: 70
>Keyup ↑ Key: "Shift" KeyCode: 16
>Keyup ↑ Key: "Control" KeyCode: 17

If you look closely, you'll notice that the F key never gets a key-down event when both Ctrl and Shift are pressed.

Being able to use Find In Path / Find in Files for a programmer is crucial.

D, for instance, doesn't have the issue:
>Keydown ↓ Key: "Control" KeyCode: 17
>Keydown ↓ Key: "Shift" KeyCode: 16
>Keydown ↓ Key: "D" KeyCode: 68
>Keyup ↑ Key: "D" KeyCode: 68
>Keyup ↑ Key: "Shift" KeyCode: 16
>Keyup ↑ Key: "Control" KeyCode: 17

So it doesn't seem to be an issue with the modifiers blocking keys, but I'm thinking that something is intercepting this set of keys. Anyone know how to track down what it is and disable it?

This topic has been closed for comments

3 Replies

Userlevel 7
You can try two things first try a difrent program and see if everything is working fine and second install visual studio on other pc and connect keybord if everything is working fine. This give more info where to look.
BlackFireDragon
You can try two things first try a difrent program
I have the same problem with Qt Creator. Ctrl + Shift + F does not work.
It turns out, this is related to Razer Cortex and the FPS keymapping. If you change the keymapping or exit out of Cortex, it should work again.