VKB-SIM

I have two issues with the Space Throttle

1- VKBDevCfg Device Configurator v0.93.26 does not recognize the Space Throttle (Mini Plus Configuration) as a Space throttle when connected to the GNX SEM module. If SEM module is disconnected Pressing "Default" correctly identifies the Space Throttle but once you connect the SEM it identifies as a S-TECS Modern Throttle Mini Plus SEM XT2. This means the calibration instructions are mismatched with the actual physical throttle, and make it difficult to determine if the device is calibrating all axes/hats properly or not

2- Installing and setting up detents, the DNT light doesn't work consistently. I have two detents, one W and one L setup. The first time I setup the two detents, the DNT light was always green, except when inside the deadzone of the L detent, when it became red. The second time I setup, the DNT light would only be green inside the dead zone of the W and only red when inside dead zone of L, otherwise not lit. I much prefer this configuration. However, due to issues trying to resolve the calibration/detection issue above, I lost this setup and the detent reverted to the first type (always green except when in deadzone of L). I would like to be able to control this but don't see any settings or any instructions anywhere on where the indicator lights could be controlled to differentiate between detent deadzone 1, deadzone 2 and no detent. Appreciate advice.

The two issues are actually surprisingly related. The modern throttle stecs has two throttle axes, the space throttle only has one. So when the throttle is misdetected as a modern throttle, it will try to apply detents to the second throttle axis - which is a grip axis on the space throttle. Your center detent will thus show up as active when your grip is not tilted to the side. Also, for that matter, all your detent deadzones will also apply on the grip sideways movement.

Oh that is very helpful to know! I played around with the grip axis and indeed the left-right one is also triggering the detent lights. Good catch. So is there a way for me to somehow override the device so it can resolve the identity crisis?

When I tested it I pretty much removed the module from the STECS and ran it off a different USB device, but of course not everyone has that option. Need to check if changing the external device from SEM/THQ/FSM to generic also works.

Uploading .cfg file as suggested by support