We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3245

Summary: Wireless Ps4 Controller gets overwritten
Product: SDL Reporter: mtlndr
Component: joystickAssignee: Sam Lantinga <slouken>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 CC: philipp.wiesemann
Version: 2.0.4   
Hardware: x86_64   
OS: Windows 7   

Description mtlndr 2016-01-22 18:41:44 UTC 
Start a SDL program with a DS4 controller in wireless Bluetooth mode, then plug in a second controller, the new controller gets assigned the index 0 again (During SDL_CONTROLLERDEVICEADDED event.cdevice.which is 0, even though the PS4 controller should be index 0).
Comment 1 Philipp Wiesemann 2016-01-22 19:13:40 UTC 
This might be no problem as long as the attached controller can be opened successfully.

The device index is not fixed. It may change for attached devices if other devices are connected or disconnected.
Comment 2 Ryan C. Gordon 2018-08-06 21:20:24 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.