Perhaps there is a reason it offers both devices, since the Xbox 360 version is actually better in my opinion, it allows both triggers to be pulled in at once but the Xbox One version puts the triggers on only one axis (so when you pull both triggers it reads zero in the middle). I'm not sure the Xbox 360 can use Xbox One controllers, I've read a website saying you can't. If the aliases behave identically and there's no problem, you are just being confused as a user You only need to remember the name of the device he wants to use anyway. Maybe installing drivers or bundled software will add their full names in the list. The SNES and PS3/PC gamepads may have no specific entry or there's no manufacturer info about them, so they stay with generic names and without alias/"real name" or they only stay there with their real name, because there is no alias for their "blueetooth interface" because USB devices are the de-facto standard to be expected (and the other interfaces pretend to be USB devices and that's why they are listed so they can be found). I think 0+2 and 1+3 they should work identically. (easier to search & find Xbox controller than for XINPUT-compatible/bluetooth in a drop down list). If there's a match for a specific entry (the alias with "real product name" for it) is added to maybe simplify finding that entry for the users. I suppose MS has an internal DB to look up ID's from the devices. It seems that the first name version also refers to the interfaces used to connect the device (bluetooth) and it's type, while the second pair describes the specific product name. First is the general generated name like "this is a mouse" and the second is the more specific "microsoft mouse 192323" name. I think it's just two different names, aka aliases, for the same thing. I don't know why it is this way, and what you mean with 2 and 3 should not be there or not working, I think they should.Īs it seems 0 & 1 and the device general group/description and the 2 & 3 are the specific description and names of those devices. The two joysticks are device 0 and 1, I'm not sure why 2 and 3 are detected. Input device 3: XBox 360 controller 2 detected Input device 2: XBox 360 controller 1 detected Input device 1: Controller (Xbox One For Windows) detected Input device 0: Bluetooth XINPUT-compatible input device detected I tried connecting two joysticks and I got this result: What is the best way to work around this? Should my game keep a database of controller name strings so I can apply the appropriate settings for each controller? I think it would be too complex for the user to configure all this themselves. The differences are expected since controllers vary in their design so it would be hard to come up with a uniform system. When a SNES controller is connected with a USB adapter it is detected as one joystick:Īlso when different controllers like Xbox and PS3 etc are connected the analogue stick readout varies and you need to read them using different "pad" values that varies between controller. Is the reason for the second one appearing known? The second controller can be safely ignore as all readouts can be obtained from the first one. When using bluetooth with the Xbox One controller I also get two devices:Ġ: Bluetooth XINPUT-compatible input device With an Xbox One controller connected by USB cable I get 2 joysticks after calling InitJoystick() I have done some initial testing of joysticks with PureBasic but I'm having some difficulty. I couldn't see a whole lot in the forum when I searched for this so thought I would post some thoughts on joystick implementation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |