r/VKB

▲ 3 r/VKB

STECS STEM longer cable?

basically just the title.. it uses a usb-c to c which they claim is non standard but how much truth is there to that, or can i just buy a longer cable from them?

reddit.com
u/aylaaaaaaaa — 3 days ago
▲ 10 r/VKB+1 crossposts

Help VKB GNX won’t calibrate

Just purchased the GNX THQ module plus the installed HID upgrade that you need to use as a standalone unit plugged directly into your computer.

I downloaded the required configuration software from VKB and went through a list of steps I could find.

During calibration, I cannot get any of the axises or buttons to show up at all. They don’t register or do anything. I’ve tried everything but no luck.

Am I missing something here?

u/svbstvnce — 8 days ago
▲ 8 r/VKB+1 crossposts

VKB shipping times

I just bought a VKB gladiator as my first Hotas and I was just wondering how long shipping usually takes. It’s kind of important at I’m shipping it to CT where I am rn for an internship but will only be here till the end of July when I will move back home. Thanks!

reddit.com
u/Significant_Tap5641 — 9 days ago
▲ 6 r/VKB

Star Citizen does not recognize VKB Sticks

https://preview.redd.it/86euekrd809h1.png?width=1149&format=png&auto=webp&s=7ed6e30341a999f64b2867c02054374642334388

https://preview.redd.it/9etsr3xr809h1.png?width=341&format=png&auto=webp&s=59f25ebb94561ea10314735eac755e6410dd8852

https://preview.redd.it/dqdrm4xr809h1.png?width=1019&format=png&auto=webp&s=eabff9e4821acb1ab0bbe62376e0c7e4dbfe3e97

I bought the VKB Gladiator EVOs for Star Citizen a while back but had problems setting up the controls from the start and since I didn´t want to tackle that at the time I let them just rest on my desk.

Now I found the motivation but its quickly turning in to furious frustration...

The Game Client doesn´t recognice the direct input (buttom presses) when I want to manually set controlls and when I try to preload profiles that the game offers it mixes up the sticks as in right stick should be pitch, roll, yaw etc. but is thrust and strafe for example.

I tried following the guides online and reset and recalibrated both sticks which didn´t help. I also tried to switch both sticks using the star citizen console but it doesn´t seem to recognize the right stick at all.

I even tried third party software to bind makros etc. but it all just doen´t want to work right

Other games (War Thunder and Nuclear Option) have no issues at all which makes it even harder for me to understand.

Idk if what I´m doing wrong but I don´t think it should be this hard to get the forsaken things to work.

Maybe some of you guys know something that will help... :/

reddit.com
u/RayBln — 14 days ago
▲ 2 r/VKB

VKB Sticks + Ubuntu Linux 26.04 = major X axis drift?

I am running Ubuntu Linux 26.04 (with KDE) and Elite Dangerous installed via Steam. (So, Proton Experimental)

I have two VKB sticks for a HOSAS setup - a VKB omnithrottle and a VKB NXT Evo + SEM module. It's the latter that is giving me fits.

The X-Axis on the VKB NXT Evo + SEM seems to be permanently stuck 3/4 of the way to the right.

- I have successfully gotten both sticks to properly be detected within Linux as joysticks. (Using protontricks to disable the gamepad detection)

- I do not have the mouse mapped to the "flight rotation" axis I am trying to configure the stick to. (And I have tried multiple bindings to other controls)

- They are both updated using the latest firmware from VKB's website (as of about a week ago?)

- Both sticks were re-calibrated on a Windows machine (since there is no Linux VKBDevCfg on Windows - that calibration was saved to both sticks, and has been verified to be good even a couple days after the fact.

- Running jstest-gtk right after plugging the device in shows a good calibration - until you move the X axis. Then, it is slammed to the right and can only be corrected by a large motion to the left.

- You *can* recalibrate using jstest-gtk or jscal, however this does not change the behavior.

- Running jscal-store /dev/input/js0 after a calibration does not seem to make any changes.

- I can take the same joystick that is showing this behavior, connect it to a Windows machine, run VKBDevCfg, and the calibration is fine. I cannot get the issue to re-occur.

I am running out of ideas here, and I *really* do not want to dual boot my desktop just yet. (Not opposed to the idea, but I would rather figure this out) I have to assume that proton is not updating its calibration, which appears to be bugged in the first place. I'm 99% certain this is not something specific to the sticks, but rather how Linux is reading them.

Any help in pinpointing something I might have overlooked?

reddit.com
u/Attila-The-Pun — 11 days ago