1.32 BUG X4 does not find all controllers. How to fix this?

[amenditman]

I have a Virpil Mongoost-50 throttle and am experiencing the same problem. Device not listed in X4 'Manage Controllers'.
My X4 is GOG, 3.30.

Throttle is detected by Windows.
A user on the Virpil forums shared a screenshot of his throttle being in the list.

Edit: Just checked the throtlle settings in Virpil software, there is a Z axis set, no X or Y.

Edit 2: Throttle has two dials, renamed them to X and Y axis. That got the controller to show up in game settings.

Edit 3: It works, but something changed is causing the mouse cursor to be confined to the game window, which it wasn't prior to change.

Advice for a workaround from Egosoft would be much appreciated.

[DocAce]

Just to be on the safe side: if you're using Steam, could you double-check that the built-in controller mapping feature is turned off for the non-working devices?

[Lilting Banshee]

in X4 properties in Steam, i have "Steam Input Per-Game Setting" set to "Forced Off" - is that the right thing?

i checked Steam's global controller settings, and the only controller it detected is the joystick. i didn't see a way to turn that off, but the stick does work fine.

[BigBANGtheory]

I recently upgraded my pedals from Saitek Combat Pro to Virpil Ace , and now I get the issue being described in this thread i.e. X4 stopped recognising my pedals even though they are visible in Windows 10 Control Panel

The axis names of the pedals are Z, Slider & Dial on the Virpil Ace.

Fortunately Virpil have a 'VPC Configuration Tool' if you go to the Pro setting you can change the axis names, which I did to X, Y & Z and now the pedals appear in X4.

So yes I would agree with previous comment that this is an issue unique to X4 and XR I didn't have this issue with Elite, Star Citizen or MS Flightsim 2020 they detected the Virpil pedals in their default setup as you would expect.

I also managed to get the Thrustmaster Cougar MFDs working by attaching them to my Thrustmaster Warthog throttle via the TARGET editor (as a combined virtual controller), again the issue is X4 not recognising the MFD as a controller in their own right (even though Windows does) something in X4 is filtering them out possibly because they have no analogue axis with the expected names.

So the good news is/was that there are work arounds BUT it shouldn't be necessary and its a right pain to setup I've spent a good 3hrs trying to figure out how to get them working.

[Lilting Banshee]

since my last post i've changed my joystick, and the VKB rudder pedals are no longer an axis on the stick. instead they have their own device with an RX axis (only). as expected, they stopped working in X4 until i went into the VKB software to change the axis from RX to X. this is with 4.00 Beta (422687).

i've also added another device, a Winwing Combat Ready Panel, which is another USB button box. this one does have two axes, but because they're RX and RY, the device doesn't show up in X4.

i guess this issue is low priority since it's only affecting a fairly small number of users with unusual hardware, but it is a bit irritating :-/

[LazzySeal]

How come this ,critical, as I think, issue for a space sim, was not fixed for ~2 years?

[CBJ]

Various issues associated with controller recognition have been fixed, so without knowing exactly what devices you have and what isn't being recognised, we're not going to be able to help you.

Since this thread is extremely outdated, I'm going to lock it and ask you to start your own thread, providing the information requested at the top of the forum as well as details of your devices and what you've tried.