LizardByte / LizardByte/libvirtualhid

Adopt registered pid.codes identities for virtual HID profiles

Aperta
#79 0 commenti 1 reazione 1 assegnatario Vedi su GitHub

@LizardByte-bot ci sta già lavorando.

Dal 15/8/2026.

Lingua principale
C++
Stelle
54
Fork
15
Merge medio
11h 32m
PR unite (30g)
34

Descrizione

Describe the Bug

This issue tracks adoption of the product IDs requested in pidcodes/pidcodes.github.com#1260.

The changes must not be made until that PR is accepted and merged. Once allocated, libvirtualhid should replace its temporary identities with the registered IDs so operating systems and consumers such as Sunshine can distinguish each virtual device profile reliably.

Expected Behavior

After the pid.codes PR is merged, libvirtualhid should use these identities:

VID:PID Profile
1209:4C56 Generic Controller
1209:4C57 Keyboard
1209:4C58 Mouse
1209:4C59 Touchscreen
1209:4C5A Trackpad
1209:4C5B Pen Tablet

The identities should be consistent across supported backends, tests, documentation, validation tools, and downstream consumers.

Additional Context

Implementation checklist:

  • Wait for the allocation PR to merge and verify the final assigned values.
  • Update the built-in profiles in src/core/profiles.cpp.
  • Audit and update hard-coded identity expectations in unit, backend, consumer, broker, and installed-driver tests.
  • Update Windows browser and installed-driver validation scripts for the Generic Controller identity.
  • Update public documentation that describes the Generic profile identity.
  • Coordinate Sunshine integration so it consumes the registered profiles without relying on temporary identifiers.
  • Update gamepad-helper and the gamepad tester to recognize the new Generic Controller identity in Firefox- and Chromium-style Gamepad.id strings. Retain recognition of the previous identity for older libvirtualhid installations where practical.
  • Document the identity migration because Steam, SDL, browsers, or other applications may treat the updated profiles as newly connected devices and reset per-device configuration.
  • Validate the affected profiles with the MinGW/UCRT64 test suite, Linux backend/consumer tests, installed Windows driver checks, and live Steam, Firefox, and Chromium testing.

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.