marvel ultimate alliance pc xbox 360 controller fix

With this being the case, Marvel Games' creative director Bill Rosemann has stated that he and his company are well aware of fans' concerns regarding the problems contained within the re-releases of the Marvel: Ultimate Alliance titles. Now, however, since the titles' official release date for the current generation platforms have come and gone, a lot of gamers have been somewhat underwhelmed by Activision's ports for PC and the latest consoles.

Use this guide to 'fix' the mapping, it will work for multiple controllers of the same kind (e.g.Marvel Games' creative director announces that the re-releases of the Marvel: Ultimate Alliance titles on current generation platforms are getting fixes and DLC.Įver since it was revealed by the Taiwan Software Ratings Board that the Marvel: Ultimate Alliance games would be getting PS4 and Xbox One ports, fans of the popular super hero franchise were clamoring for practically any piece of information that they could get their hands on. Be aware, that with the LATEST driver, the triggers of the ONE controller behave as 'Z' and 'Rotation Z' axis, while in the 360 WIRED the triggers behave as a single Z axis.ĮDIT: Thanks to the post about xinputplus from machine4578, i realized that in the re-release the dpad must output buttons 13 to 16 instead of POV.

but a little more complicated to understand. Now here's a table of how the 360 wired and xbox one controller work in DirectInput mode, its more complete than the previous pics. It seems the developers dont know how to do proper testing, maybe they dont have many gamepads nor windows 8 or 10. For the DirectInput, the layout the developers used is different than the common DirectInput layout of Xinput controllers.Īnd besides that, the layout used for this rerelease is different to one in the original release, hence why in the original the Y button remained as Jump, while in this B still works as Strong attack and cancel. If it is not correctly recognized as an XInput controller, it falls back to DirectInput, and here is where the problem shows. Third party controllers like the logitech ones and the wireless 360 controller with adapter suffered wrong button mapping.Īpparently the game read something else beside the api, something like the name of the device or the hardware id.

Only the WIRED 360 controller worked as it should. Since the first release, the way the xinput api was implemented was broken. I'll try to explain what i've observed, and hopefully a competent dev sees this post, understands it and is able to fix the problem that has been an issue for 10 years already. Ok, i see many of you have no idea what the technical issue about the controller is, and false or wrong information is going around creating a lot of missinformation.

Marvel ultimate alliance pc xbox 360 controller fix