Connecting an xbox one controller and playing for sometime seems to trigger some weird bug that basically breaks the entire modern UI including settings app, game bar, and even the mouse pointer when using snip and sketch to cut a screenshot, the mouse pointer moves up.
The problem might look like it can be easily resolved by disconnecting the controller and reconnecting again. except it's not. disconnecting the controller does not stop the weird behavior. my controller is now disconnected and Windows UI is still reading 'UP' from the left analog stick. It's not a hardware issue with my controller or my USB ports/cables. Trying services like "html5gamepad.com" does not return any indications that any keys were being pressed.
To achieve this, you can use the Startup Applications app (search for it into applications menu) and create a new entry from the GUI, or simply create a xbox-controller-driver.desktop file inside .config/autostart folder including the content below:
This is the final release of 360Controller (barring some big issue with the creation of this release). This is due to the new DriverKit system that Apple is implementing in favor of kernel extensions. My focus will now be on working on this DriverKit solution. No further updates will be made to this driver by me (@FranticRain).
This is an early release of a modern rewrite for this driver. It updates the driver to the modern standard and re-implements wireless controller support. If you find any regression in the driver, make sure to make an issue and specifically mention that you are using this version of the driver.
This is an early release of a modern rewrite for this driver. It should exactly match the functionality of the existing driver. So wireless controllers are still not supported at this time, but your wired controllers should work exactly as intended. If you find any regression in the driver, make sure to make an issue and specifically mention that you are using this version of the driver.
This is the first pass at a modern rewrite for this driver. It should exactly match the functionality of the existing driver. So wireless controllers are still not supported at this time, but your wired controllers should work exactly as intended. If you find any regression in the driver, make sure to make an issue and specifically mention that you are using this version of the driver.
There are a couple new devices added in this release, along with some some safety features so that old versions of the driver don't come back to haunt you. Primarily, this release is for new devices and some fixed version stuff.
It looks like the hang on boot that some users were experiencing was caused by the Xbox One controller Bluetooth support hooks that had been added to the driver. In order to resolve those issues, all Bluetooth support has been removed from the driver. Simply put, if you are using the controller via Bluetooth, the driver won't do anything for you. Please do not install older versions of the driver in order to get the force feedback over Bluetooth support and then post an issue about your computer hanging on boot.
To enable gamepad support, ensure that you have installed the latest version of the NICE DCV Server and that you opted to install the Gamepad driver. For more information, see Installing the NICE DCV Server on Windows. When the driver is installed, the feature is enabled by default on Windows NICE DCV servers.
Windows 10 has a native driver system embedded in the OS. By keeping your device up-to-date, you will ensure that you are always running the latest software or hardware drivers, as Microsoft frequently fixes known issues. View instructions to check for the latest updates for your Windows 10-based device.
The reason why we looked into the Mayflash / TigerGame driver is a few years back we did a blog about the original Xbox controller and how to get these relics from the past working on your Windows 10 box. It worked, however, it quickly became the most commented section on our blog and for those who commented there I want to say "Thank you!" Your input makes a very important impact on how we do things on our site, what works, and what doesn't. It's apparent that there are a lot of you guys out there that love your old-school hardware.
Along with the love and thanks, there was obvious frustration over the XBCD driver. But this had more to do with Windows 10 as an operating system than the driver itself. You see, the XBCD blog had to discuss some complicated issues. Such as Windows 64-bit you had to disable signature enforcement to install this driver as it predates signed drivers.
In some desktops and laptops a feature loaded called "Secure Boot" was also plaguing users with code 39 errors. Stripping out these layers of security from windows 10 is daunting for a new user and you shouldn't have to fight with your OS over a joystick worth $10 bucks. So we started to scan the net to see if anyone actually made a signed version of the XBCD driver. We found something interesting!
In the early days of gaming, there really was no standard as to how to hook a joystick up to a console or PC which lead to some interesting ways to hook up those joysticks and gamepads. However, USB 1.0 (originally released in the mid to late 1990s) was around for systems such as the Sega Dreamcast, the Xbox Original, and The PlayStation 2. But for some reason, the video game industry as a whole decided to turn its back on such standards. And instead, continue onward with building their own proprietary standards which still exist to this very day.
We found that there were gaming sites that weren't referencing the Mayflash site that you see today. But to a very different site which was at the time of writing this blog running parallel with their current site. The jackpot is that even though their hardware was not anything special as we'll get into later in this article. But the Jackpot was the drivers that they were providing were digitally signed for Windows Vista 64-bit. This ladies and gentlemen is gold!
The software doesn't really appear to be made by "Mayflash" or this mythical "TigerGame" company. But it seemed like they were using another developer's code to package in conjunction with their hardware. They were using drivers from the Xinan Ruida Electronic Factory which if you google their name you'll get countless other knock-off third-party adapters not necessarily made by Mayflash appearing on Amazon. Perhaps this could be another reason why Mayflash wants to walk away from this sketchy part of their company history.
We as bloggers strongly encourage users to go buy a product from those who help them. Mayflash as a business doesn't seem overly interested in selling directly to the public as much as they want to place themselves as a manufacturer. There are still vendors on eBay which will happily sell you an official Mayflash Xbox adapter for under $10. As for the website, Mayflash sometimes has 404 error-ed on all of the sites as I was editing this entry! This PDF is the only proof I have to give to you indicating anything dealing with their product's raw existence which at the time Mayflash was interested in bulk orders for redistributors. eBay - has a large assortment of generic non-may flash cables that will work with this driver perfectly fine for under $10. Amazon - also has these generic cables available as well! Thanks for Mantis Toboggan M.D.4 for finding links and the proper name for these cables. Either link you choose to buy a cable just know that we don't many any money providing Ebay or Amazon links and just do it as a service for those interested in purchasing the adapter versus building one.
Because of the simple fact that it has to pass some registry commands so that when you plug in your joystick it will know right away what to do with it. You're going to need to give the Mayflash driver higher permissions. Ironically it says "TigerGame Superjoy Box Series Setup" and not Mayflash at all. Click the "Yes" button to continue.
 2e380cc55c