I have a USB wired Xbox 360 controller that works fine. The Xbox One controller is connected by Bluetooth and it works fine too.
I have and old Xbox 360 wireless controller but the pad was damaged and I do not have any other pads to try.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
When connecting the Xbox One S controller via bluetooth, many games suffer performance problems.
This is remedied by plugging it in via usb.
Firmware updates so far have not remedied the problem.
Just a brief anecdotal example before I demonstrate the scope of this problem
Just Cause 3's menu screen is locked to 30fps.
With KB+M: 30fps
XBone S via bluetooth: 22fps
XBone S via usb: 30fps
Now, this issue has come up in many forums over across the internet.
http://steamcommunity.com/app/462780/discussions/0/154642447923607852
http://forums.ubi.com/showthread.php/1554736-Bluetooth-Xbox-Controller-FPS-DROP-glitch-Forums
http://forums.ubi.com/showthread.php/1586804-Problem-controller-with-cable-vs-Wireless-Forums
How do we get some dev attention on this issue? It's widespread and affects many games, and seems to be a driver issue.
I've tried updating from the current live release to the most recent insider build, as well as buying a high end bluetooth adapter. The issue persists, and clearly has nothing to do with me, my config, or anything we as users can do.
I've taken a fresh format, installed Trials Fusion(this game is particularly bad, unplayable over bluetooth0, and could immediately see the issue in play.
I've even swapped GPUs, from AMD to nVidia (not in an attempt to fix this, but it rules out display driver related issues)
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I have a USB wired Xbox 360 controller that works fine. The Xbox One controller is connected by Bluetooth and it works fine too.
I have and old Xbox 360 wireless controller but the pad was damaged and I do not have any other pads to try.
The whole idea of using the controller though is for the native support. If the native support doesn't exist then there is no reason to use an Xbox controller at all since there are better options. I agree with your resolution. I am just using a different controller that's wired in. But it's asinine that an Xbox controller would wreak so much havoc on a Windows machine. Amateur hour from Microsoft.
Guys just use 8BitDo wireless adapter. I gave up on this problem long ago and tried the adapter and it works fine. Seems a big bug on normal bluetooth connection.
I am experiencing major FPS drop in Assassin's Creed Odyssey (via Uplay). Similar to the person who noted 4 FPS for stretches I am having the same thing. It is virtually unplayable when this happens. I have no issues whatsoever when using a Nacon Revolution Pro v2 in it's place.
Current build:
CPU: i7-8700k 3.7GHz
GPU: RTX 2080 8GB
RAM: 16GB DDR4
This PC is 2 weeks old. I spent hours with Ubisoft support trying to fix this thinking it was due to their recent patch (the same day I got my XB1S controller in) and so I've already uninstalled and reinstalled every driver on the planet, only to discover the issue immediately went away as soon as I switched to M&KB (note the XB controller was still connected, just not the active controller in-game (it's a setting in Odyssey's game options to switch instantly)).
I find it absolutely mind boggling that a Microsoft controller doesn't work on a Microsoft system. People mock Apple users (I've used and played on Macs for over a decade) yet everything works there, especially if it's peripherals by Apple. This should be an absolute embarrassment to Microsoft. 2 years and the issue persists.
Suffering from the same problems. Most noticeably in Assassins Creed Origins with frames dropping to 4 fps for up to a minute at a time.
Running:
Windows 10 Pro build 1809
AMD 1920x
32GB
1080ti
It actually worked flawlessly for the first 10-20 hours or so then got consistently unplayable. Hopefully something gets a patch.