自定义Windows游戏手柄处理实现方案技术咨询

Great question! Your core idea of inserting a middle layer between the physical gamepad and Windows' controller management is totally solid—let's walk through each step with concrete implementation details to make this work.

The key here is to let your program read the physical pad directly while preventing Windows from recognizing it as a standard game controller. Two practical approaches:

• Use devcon to selectively disable the game controller driver:
  First, find your pad's hardware ID (go to Device Manager → Game Controllers → Right-click your pad → Properties → Details → Hardware IDs). It'll look like HID\VID_XXXX&PID_XXXX.

  Then run Command Prompt as Administrator and execute:

  devcon disable "HID\VID_XXXX&PID_XXXX"
  

  This disables the system's game controller driver for the pad, but keeps the HID driver active—so your program can still read it via low-level APIs, while Windows won't show it in the controller settings. To re-enable it later, replace disable with enable.

• Write a HID filter driver (advanced):
  For full control, you can create a lightweight filter driver that intercepts Windows' requests for the pad's game controller interface. This is more complex but avoids relying on devcon—only recommended if you have Windows driver development experience.

First, set up the vJoy ecosystem:

1. Download and install the vJoy Device Driver (make sure to get the compatible version for your Windows build).
2. Open vJoyConf.exe (installed with the driver) to configure your virtual controller: match the number of axes, buttons, and POV hats to your physical pad, then enable the virtual device (usually ID 1).
3. Install the Python wrapper:

   pip install pyvjoy
   

Here's a quick initialization snippet:

import pyvjoy

# Target virtual device ID (matches what you set in vJoyConf)
VJOY_DEVICE_ID = 1
virtual_joy = pyvjoy.VJoyDevice(VJOY_DEVICE_ID)

# Reset the virtual controller to a clean state on startup
virtual_joy.reset()

Use one of these libraries to read raw input from your unbound pad—no need to go through Windows' controller stack:

Option 1: inputs (Simplest for Most Pads) #

This library handles most common gamepads out of the box with minimal setup:

from inputs import get_gamepad
import time

def read_physical_pad():
    while True:
        events = get_gamepad()
        for event in events:
            # Handle axis input (e.g., Left Stick X)
            if event.code == "ABS_X":
                # Convert inputs' range (-32768 to 32767) to vJoy's default range (0 to 32767)
                vjoy_value = event.state + 32768
                virtual_joy.set_axis(pyvjoy.HID_USAGE_X, vjoy_value)
            
            # Handle button input (e.g., A button)
            elif event.code == "BTN_SOUTH":
                # vJoy uses 1-based button numbering
                virtual_joy.set_button(1, 1 if event.state else 0)
        
        # Add a small delay to avoid hogging CPU
        time.sleep(0.01)

Option 2: pygame (Good for Game Dev Experience) #

If you're familiar with pygame, it's another reliable choice:

import pygame
import time

pygame.init()
physical_joy = pygame.joystick.Joystick(0)
physical_joy.init()

def read_physical_pad():
    while True:
        for event in pygame.event.get():
            # Axis motion (e.g., Left Stick Y)
            if event.type == pygame.JOYAXISMOTION:
                # Convert pygame's -1.0 to 1.0 range to vJoy's 0-32767
                vjoy_value = int((event.value + 1) * 16383.5)
                if event.axis == 1:
                    virtual_joy.set_axis(pyvjoy.HID_USAGE_Y, vjoy_value)
            
            # Button press/release
            elif event.type == pygame.JOYBUTTONDOWN:
                virtual_joy.set_button(event.button + 1, 1)
            elif event.type == pygame.JOYBUTTONUP:
                virtual_joy.set_button(event.button + 1, 0)
        
        time.sleep(0.01)

Option 3: hidapi (Low-Level Control) #

For niche pads or custom HID reports, use hidapi to directly read raw HID packets. You'll need to know your pad's report format (check the manufacturer's docs or use tools like HIDExplorer).

• Range Conversion: Always double-check the input range from your physical pad library and map it to vJoy's configured range (adjust in vJoyConf if needed).
• Performance: The time.sleep(0.01) in the loops keeps CPU usage low while maintaining responsive input.
• Error Handling: Add checks for disconnected devices or uninitialized virtual controllers—for example:

  try:
      virtual_joy = pyvjoy.VJoyDevice(VJOY_DEVICE_ID)
  except pyvjoy.VJoyNotFoundError:
      print("Error: Virtual vJoy device not found! Make sure vJoyConf has it enabled.")
      exit(1)
  

• Multi-Pad Support: If using multiple physical pads, filter events by device ID or VID/PID to avoid mixing inputs.

• Admin Rights: Both reading HID devices and interacting with vJoy often require administrator privileges—run your script or IDE as Admin.
• vJoy Driver Compatibility: On Windows 11, you may need to disable driver signature enforcement temporarily to install the vJoy driver.
• Pad Compatibility: If inputs or pygame don't recognize your pad, use hidapi with a tool like HIDExplorer to reverse-engineer the HID report format.

内容的提问来源于stack exchange，提问作者Kefir