360Controller / 360Controller/360Controller
PDP Afterglow Prismatic Wired Controller not responding (or appearing)
- Langage dominant
- C++
- Étoiles
- 6.7k
- Forks
- 524
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
### Type of Controller
Xbox One
### OS Version
MacOS Monterey 12.5
### Driver Version
Latest as of Friday, August 12, 2022
### Connection Method
Wired (USB A to USB Micro); several different cables have been tried with no luck
### Device Name and Info
> Device Name: PDP Afterglow Prismatic Wired Controller for Xbox
Product ID: 0x0139
Vendor ID: 0x0e6f
### Response of Controller
No response upon plugging in whatsoever. I've tried multiple cords. At one point (out of curiosity), I plugged it into a live charging cable. The lights inside the controller flashed for a brief fraction of a second, then resumed their unresponsive state.
### Response in Preference Pane
"No devices found"
### Detailed Explanation of Issue
System Information recognizes the controller as "Afterglow Prismatic Wired Controller for Xbox One" and gives all the information...
But it's not showing up in the extension. :(
PDP is no help. I suspect that it might be a problem with the controller itself (I recently updated the firmware on it from an Xbox using the PDP Control Hub app -- that might be the cause of this, but I don't think so for no reason whatsoever), but that seemingly contradicts its showing up in System Info... What do I do? Pester PDP? (Hmm... that sounds fun)
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
The issue describes a specific PDP Afterglow Prismatic Wired Controller (Vendor ID 0x0e6f, Product ID 0x0139) not being recognized by the driver, though it appears in System Information. Start by examining the driver's USB device matching logic, likely in source files handling vendor/product IDs. Check if this PID/VID pair is listed in the supported devices. The user mentions a firmware update via PDP Control Hub; research if this changed the controller's USB descriptors. Testing would require the physical hardware to verify any code changes.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- c, cpp, macos
- Domaine
- desktop
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 30/100