Same... Only my right stick and pedals are showing up as inputs.. I need 3 inputs... Right Stick, Pedals, and Throttle...
Virpil MongoosT-50 Throttle.
- NSAT
Same - my VIRPIL T-50 isn't being recognized at all. No issues in other games, no issues with Windows, already forced off Steam input configurations and disabled steam's general controller settings but still no dice. My Sidewinder FFB is being recognized for whatever thats worth.
I'm really just thinking about doing a refund at this point - very disappointing.
FWIW I just got the MongoosT-50CM2 Throttle and after a firmware update to 20200925 it's recognized.
I've tried updating the firmware on my T-50 (original version, not CM2) to 20200925, but it makes no difference in SWS.
My T-50CM2 stick base and T-50CM throttle are detected but I can't assign any axes. Every time I hit assign it grabs "Slider 1 Up" no matter what I'm doing, my guess is the brake lever of the VFX grip is setting it off despite no issues assigning bindings in games like DCS. Worse still, it's calling my throttle "stick 1" and button 1 of the throttle is actually a two-way toggle between button 1 and 2 so there's no way to get through menus with it plugged in.
None of this would be nearly as frustrating as it is had they not made the unfortunate decision to make any plugged in controller override mouse and keyboard in the menus. That's the kind of mistake made by console developers expecting you to play their PC game with a console controller.
Im having a similar issue - throttle shows up as stick1 but not my grip.
Anyone figured this out?
I have the T50CM2 throttle, t50cm2 base, and constellation alpha grip
i occasionally have this issue when assigning axis in games. It can usually be fixed by finding the input that is sending the erroneous command and then running that axis through its full range of motion.
once you’ve done that it should see the trouble makers full range and the input spike should be gone.
you can also check this in windows in the USB controls. Find the device that’s the trouble maker and open the properties for it. You’ll see all the inputs and likely see one of the inputs spiking.
if it continues to be a problem try recalibrating or assigning the to test dead zone to make up for it.
