Problem with VKB T-Rudder not working properly.

[kieldunn2125-prog]

Hello, I've been trying to setup my sticks and rudder to work with arma, with vjoy gremlin and 360ce.
I have all drivers properly installed, and have tried multiple versions of each program.
In tools input viewer, and calibration my rudder works fine, and is moving around, but it doesn't work to 360ce, or "grey out" when trying to find axis. Now if I move over to my gladiator, and use my axis there, they grey out, and immediately when moving back to trudder, if I move the axis it greys out once to my x axis. Then it doesn't work again.
This is an insanely strange problem, that I'm not sure how to fix. Doesn't make any sense to my why it works after specifically moving to another device, getting a grey, then moving back. it doesn't work if I don't do that specifically.
really I just want to play video games but I feel like I need a PHD to not use a mouse/controller.

[WhiteMagic]

There are many moving parts in this and I don't know that unpacking them here will work out well. You may have better luck on the HOTAS discord in the #joystick-gremlin channel where a bunch of people help trying to debug and work out things. A few comments/ideas though:

• You should not need 360CE for Arma (unless you're talking Arma Reforger (don't know their state of joystick support) and not Arma 3)
• I have no experience in wrangling vJoy output into an XInput device, though people on the discord have
• When you say multiple versions things get dangerous. For Gremlin you should only need the latest (13.3 / 13.3debug) and the vJoy version mentioned in the documentation. Anything else will bring trouble. For 360CE I have no insights.
• Gremlin on its own should be fine with those devices so to narrow down where things go wrong I'd just use Gremlin without 360CE for a basic setup and similar for 360CE without Gremlin for a basic setup, just to verify the tools are happy independently.