[XBOX ONE] Problems with other controllers? - FIX INSIDE!!
Posted: Tue Jun 09, 2015 5:44 am
Here is a post that was made by @J2Kbr regarding the recent problems we've been seeing with Titan One users that are using the Xbox One *console* with any controllers other than the official Xbox One controller (e.g., DualShock 4 or Xbox 360). The most recent update to the Xbox One made some changes to the way that the controllers interact with the console. This causes the Xbox One controller to automatically re-authenticate with the Xbox One right after the Titan One authentication. The solution is to make sure your Xbox One controller is powered down after it authenticates the Titan One. @J2Kbr is working on a more elegant solution to this!
The best way to fix this issue is to remove the batteries from your Xbox One controller before using it for authentication!
The best way to fix this issue is to remove the batteries from your Xbox One controller before using it for authentication!
J2Kbr wrote:Confirmed. the latest XB1 update changed how the connection controller/console is handled. I'm investigating it and working to fix.
As a temporary workaround make sure to turn off the XB1 controller before unplug it from the Titan One. It can be done using the Device Monitor or by the script below (pressing A after the authentication).
- Code: Select all
main {
if(event_press(XB1_A)) {
turn_off();
}
}
EDIT: Another solution would be remove the battery from the XBox One controller, doing so the controller can not connect to the console wirelessy.
The problem happens when the controller detects the usb cable was disconnected and try connect to the console wirelessly. Before the update this was not a problem because the USB connection had higher priority, but seems the update changed that, favoring the wireless connection over the usb connection.