Mantis

View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0019559Runner[All Projects] Input DevicesPublic2015-11-17 21:142017-08-04 16:54
ReporterTeddy Diefenbach 
Assigned ToFritz 
PriorityHighSeverityB - MajorReproducibility100%
StatusClosedResolutionFixed 
PlatformWindows 10OSWindows 10OS Versionver 10, build 10
Summary0019559: Input Devices: Xbox One controller takes 2 ports
DescriptionWhen plugging an Xbox One controller into a Windows 10 machine, it registers input into ports 0 and 1. This specifically happens with JUST the first Xbox One controller plugged in. i.e. the first controller plugged in takes slots 0 and 1. The second controller takes only slot 2.
Steps To ReproduceRun game in Windows 10
Plug in Xbox One controller
use gamepad_is_connected to see that 0 and 1 are both receiving input from this controller
1.4 VersionEA1.99.460
2.x Runtime Version
2.x Runtime Version Verified In9.9.1.670
Attached Files? file icon TwinStickShooter_Complete.yyz [^] (145,984 bytes) 2017-02-20 12:32

- Relationships

-  Notes
(0040684)
Stewart Bishop (Administrator)
2015-11-18 16:51

We'd need a sample from you which shows this as this isn't something I've heard of personally.
(0043304)
chromo (Updater)
2016-05-13 16:09

I've found this too, but only on disconnection. If an Xbox One pad is connected, it will appear for me as 0. If it is then disconnected and then reconnected, it will appear as both 0 and 4.

Reproduced using the code found on the GM Blog here http://www.yoyogames.com/blog/75 [^]

Pad will simultaneously report as 0 and 4 on reconnection.
(0051676)
Daniel Cleaton (Administrator)
2017-02-20 12:26

Have now reproduced using a Xbox One Elite pad - a regular Xbox One pad doesn't seem to cause this for me in this sample.
(0051751)
Daniel Cleaton (Administrator)
2017-02-24 15:59

Still reproduces for me using the same steps as before the attempted fix:

1. Start the IDE and import the attached project.
1. Have the pad plugged-in.
3. Run the game.
4. All okay.
5. Unplug the pad's USB cable at the pad end. Wait a few seconds.
6. Plug the pad's USB cable back in to the pad.
7. Observe loop of finding/losing the pad.
(0051752)
Daniel Cleaton (Administrator)
2017-02-24 16:23

Going to spin the above out as a new report, as it differs from the original, and re-resolve this one.


Copyright © 2000 - 2017 MantisBT Team
Powered by Mantis Bugtracker