Associate
- Joined
- 1 Feb 2019
- Posts
- 11
- Location
- Sussex, UK
I was wondering if anyone else has hit this problem before.
As a Linux gamer, I have to buy "Windows" keyboards, and while I obviously don't have access to the macro and lighting software, they do at least function properly as keyboards. Apparently... not this one. Roccat Vulcan 80, firmware 1.15 (latest)
Also attached to a KVM, when it initialises to Linux, it starts spamming "a" until a key is pressed... and after that, the first "a" struck, doesn't register, and then it gets back to normal.
Normal, however, includes a feature whereby if caps lock is pressed too often, then it starts spamming "a" again. Which is not funny for games that require caps lock... as suddenly I can find myself strafing left. Not much fun.
Of course, under Windows 7, it works fine.
I contacted Roccat on Monday evening, and it's now Friday morning and I haven't heard anything. Is this kind of behaviour/response typical of Roccat in other peoples experience... and if so, does anyone know of any way around this? I do actually like the keyboard a lot... it ticks my boxes technically speaking... it's just this pain of a firmware issue, and Roccat's lack of engagement.
As a Linux gamer, I have to buy "Windows" keyboards, and while I obviously don't have access to the macro and lighting software, they do at least function properly as keyboards. Apparently... not this one. Roccat Vulcan 80, firmware 1.15 (latest)
Also attached to a KVM, when it initialises to Linux, it starts spamming "a" until a key is pressed... and after that, the first "a" struck, doesn't register, and then it gets back to normal.
Normal, however, includes a feature whereby if caps lock is pressed too often, then it starts spamming "a" again. Which is not funny for games that require caps lock... as suddenly I can find myself strafing left. Not much fun.
Of course, under Windows 7, it works fine.
I contacted Roccat on Monday evening, and it's now Friday morning and I haven't heard anything. Is this kind of behaviour/response typical of Roccat in other peoples experience... and if so, does anyone know of any way around this? I do actually like the keyboard a lot... it ticks my boxes technically speaking... it's just this pain of a firmware issue, and Roccat's lack of engagement.
Last edited: