STEAM-GROEP
Big Picture bigpic
Lid worden van groep
STEAM-GROEP
Big Picture bigpic
25,057
LEDEN
771
IN SPEL
4,662
ONLINE
Opgericht
10 september 2012
Overzicht Aankondigingen Discussies Evenementen Leden Opmerkingen
APoliTech
3 mrt om 15:37
Flydigi Vader 5 Pro detected twice / inconsistent detection depending on startup order (Steam Beta)
Controller: Flydigi Vader 5 Pro
Steam Client: Beta
Software: Flydigi Space Station (Allow 3rd-party controller configuration enabled)
OS: Windows 11

--------------------------------------------------
Issue
--------------------------------------------------
Steam detects the controller inconsistently depending on the startup order between Steam and the controller.

Sometimes Steam initializes:
• Both devices (gyro + XInput)
Other times:
• Only XInput appears

--------------------------------------------------
Reproduction Steps
--------------------------------------------------
Case 1 – Works correctly
1. Turn ON the controller first
2. Start Steam

Result:
• Steam detects controller correctly
• Configuration loads
• I see two inputs:
- Gyro / HID device
- XInput device
• Controller works normally

Case 2 – Issue appears
1. Start Steam
2. Turn ON the controller

Result:
• Detection is inconsistent
• Sometimes only XInput initializes
• Gyro / second device does not appear

--------------------------------------------------
Additional Issue
--------------------------------------------------
When ONLY XInput initializes:
• Pressing the controller power button does NOT turn off the controller
• The controller gives a very short vibration
• Controller stays powered on

When both inputs initialize correctly:
• Controller turns off normally

Also important:
Even when everything works correctly, Steam still detects TWO inputs for the same controller.

--------------------------------------------------
Log Observation
--------------------------------------------------
Working scenario:
Steam opens:
Flydigi Vader 5 Pro (HID / gyro)
XInput Controller #1

serial_number: - 0 [2026-02-27 17:40:41] Manufacturer: [2026-02-27 17:40:41] Product: Flydigi Vader 5 Pro [2026-02-27 17:40:41] Release: 1 [2026-02-27 17:40:41] Interface: -1 [2026-02-27 17:40:41] !! Steam controller device opened for index 0. [2026-02-27 17:40:41] Steam Controller reserving XInput slot 0 [2026-02-27 17:40:41] Local Device Found type: 37d7 2401 path: sdl://12 serial_number: - 1 [2026-02-27 17:40:41] Manufacturer: [2026-02-27 17:40:41] Product: XInput Controller #1 [2026-02-27 17:40:41] SDL Mapping for 37d7/2401: 03003989d73700000124000001006815,*,a:b0,b:b1,back:b4,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b5,leftshoulder:b9,leftstick:b7,lefttrigger:a4,leftx:a0,lefty:a1,rightshoulder:b10,rightstick:b8,righttrigger:a5,rightx:a2,righty:a3,start:b6,x:b2,y:b3,paddle1:b11,paddle2:b12,paddle3:b13,paddle4:b14,misc2:b15,misc3:b16,misc4:b17,misc5:b18,misc6:b19,crc:8939,platform:Windows, [2026-02-27 17:40:41] Release: 1 [2026-02-27 17:40:41] Interface: -1 [2026-02-27 17:40:41] Controller using HIDAPI driver, vid=0x37d7, pid=0x2401 [2026-02-27 17:40:41] !! Steam controller device opened for index 1. [2026-02-27 17:40:41] Controller has an Invalid or missing unit serial number, setting to '37d7-2401-62fb2a4' [2026-02-27 17:40:41] Steam Controller reserving XInput slot 1 [2026-02-27 17:40:41] SDL Mapping for 37d7/2401: 0300fa67d73700000124000001007801,*,a:b0,b:b1,back:b6,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b10,leftshoulder:b4,leftstick:b8,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b9,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,platform:Windows, [2026-02-27 17:40:41] Controller has an Invalid or missing unit serial number, setting to '37d7-2401-62fb2a4g' [2026-02-27 17:40:41] ConfigSet - found config set file on-disk: C:\Program Files (x86)\Steam\steamapps\common\Steam Controller Configs\103789220\config\configset_37d7-2401-62fb2a4.vdf [2026-02-27 17:40:41] ConfigSet - found config set file on-disk: C:\Program Files (x86)\Steam\steamapps\common\Steam Controller Configs\103789220\config\configset_controller_generic.vdf [2026-02-27 17:40:41] Set Account Config Sets 0 0 0

Issue scenario:
Only:
XInput Controller #1
2026-02-27 17:40:41] Manufacturer: [2026-02-27 17:40:41] Product: XInput Controller #1 [2026-02-27 17:40:41] SDL Mapping for 37d7/2401: 03003989d73700000124000001006815,*,a:b0,b:b1,back:b4,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b5,leftshoulder:b9,leftstick:b7,lefttrigger:a4,leftx:a0,lefty:a1,rightshoulder:b10,rightstick:b8,righttrigger:a5,rightx:a2,righty:a3,start:b6,x:b2,y:b3,paddle1:b11,paddle2:b12,paddle3:b13,paddle4:b14,misc2:b15,misc3:b16,misc4:b17,misc5:b18,misc6:b19,crc:8939,platform:Windows, [2026-02-27 17:40:41] Release: 1 [2026-02-27 17:40:41] Interface: -1
--------------------------------------------------
Question
--------------------------------------------------
Is this expected behavior with Flydigi controllers in Steam Input?

Could Steam be switching between HID/DInput and XInput depending on initialization order?

Should both devices always appear?

--------------------------------------------------
Extra Info
--------------------------------------------------
I already provided logs to Steam Support and they recommended posting here.

I can provide more logs or testing if needed (I work in software QA).
< >
1-2 van 2 reacties weergegeven
Squilliam
13 mei om 8:53 
Similar weird detection issues on Steam with the Vader 5 Pro on my end, but I found it became more consistent when I disabled Steam's Xbox extended feature support driver, and disabled 3rd-party controller configuration in Space Station. If you care about either of those features I'm not sure what to do.
#1
APoliTech
3 jun om 8:27 
Update: I found the issue.

Windows had an Xbox 360 Controller entry active in Device Manager, which made the Flydigi Vader 5 Pro show up as an additional XInput/Xbox 360 controller instance in Steam.

That seems to be why Steam sometimes detected the controller twice, or behaved differently depending on whether I started the controller before Steam or Steam before the controller.

After disabling the Xbox 360 Controller entry in Windows Device Manager, Steam now detects the controller correctly and the duplicate entry is gone.

Maybe Steam could either ignore this duplicate XInput/Xbox 360 entry, or show some kind of warning that an extra Xbox 360 Controller device is active. I’m not sure if this is enabled by default, installed by Windows, or created by the Flydigi software, but it was the cause in my case.
#2
< >
1-2 van 2 reacties weergegeven
Per pagina: 1530 50

Alle discussies > Hardware, Controllers + TV Setup > Details van topic
Geplaatst op: 3 mrt om 15:37
Aantal berichten: 2
Een nieuwe discussie starten
Regels en richtlijnen voor discussies