[support for Flydigi vader 5 pro] <Flydigi vader 5 pro>飞智黑武士5pro

Controller name
Flydigi vader 5 pro

Conroller VID & PID
以下是游戏内Debug Dump的信息：
Here's my Controlify debug dump

CONTROLIFY DEBUG DUMP - 2026-07-24T10:24:26.6747886

Controlify version: 3.1.0+26.2-fabric
Minecraft version: 26.2
Client
  SDL3 loaded: true
  Platform: win32-x86-64

  Controller-manager: dev.isxander.controlify.controllermanager.SDLControllerManager
  Connected Controllers:
    Name: Controller (Flydigi Vader 5 Pro)
    Identified type: ControllerType[friendlyName=null, mappingId=default, namespace=controlify:default, forceJoystick=false, dontLoad=false]
    GUID: 0300925cd73700000124000000000000
    UID: 9cd77d254e31ad56dcb3267f60a85fb0-2
    UCID: SDL-1
    HID: HID[VID=0x37d7, PID=0x2401]
    Input Component:
      Definitely gamepad: false
      Available inputs:
    Rumble supported: false
    Trigger rumble supported: false
    Battery level: Unknown[]
    Gyro supported: false
    Touchpads supported: 0
    HD haptics supported: false
    Log:
      [10:24:26]  [Controller #SDL-1] Creating controller: 1
      [10:24:26]  [Controller #SDL-1] Controller is gamepad: false
      [10:24:26]  [Controller #SDL-1] SDL GUID: 0300925cd73700000124000000000000
      [10:24:26]  [Controller #SDL-1] SDL Serial: null
      [10:24:26]  [Controller #SDL-1] SDL VID: 14295 PID: 9217
      [10:24:26]  [Controller #SDL-1] SDL Connection State: UNKNOWN
      [10:24:26]  [Controller #SDL-1] SDL GUID driver signature: Unrecognised: 00 '

Start with the SDLControllerManager entry point named in the debug dump and inspect how the Flydigi Vader 5 Pro is identified from its GUID and VID/PID. Check the controller support and mapping paths for HID VID 0x37d7 and PID 0x2401. Done means the device is recognized with usable controller inputs rather than as an unrecognized joystick.