Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
6 
Report this post
Linked my input file in that post. Try using it. Still a big hassle having to create the profile in the first place.
Thanks Kitani, that fixed my problem as well with the Xbox One controller, developers should fix it up as well..
This was 'fixed' by just remapping, which is exactly what we advised. :)
I mean no disrespect (and I hope I don't sound snarky, but alas text over the internet) but is there any plans to fix this as the developer? It's not up to your customers to apply their own fixes for such a basic thing, and as a developer myself, I'm not sure why this is such a problem that's been going on for such a long time.
Is it the engine you used? The Xbox 360 and One controller is just XInput which most engines have default support for. I have come across similar controller issues and will try the fix, but I'm disappointed that this is an issue that's being advised as "remap it yourself" rather than a fix on your end.
Again, no disrespect, it's just rather mind-boggling that this has been an issue for so long.
We simply can't support and detect every single config and controller, so we figured that offering the ability to quickly remap is the simplest solution. Apologies if you don't think this is suitable.
Apparently the Unity engine just doesn't like the X-Box One controller when using Windows 10 and as such there's (very likely) no way for the devs to fix this issue. You'd have to wait for an engine update and then the devs would have to move the game onto the updated version of Unity, which is not as easy as it sounds.
I have the same problem with this game and the Xbox One controller on Windows 10 Pro. In fact, this issue is very prevalent throughout many Unity Engine games in my experience, usually resulting in the analogue stick acting as if it is being pushed left when it isn't.
Maybe the real issue is the diver, which Microsoft do not seem in any hurry to fix (I reported the issue direct to them last July!), but the fact remains that it can be fixed as Ori and the Blind Forest was recently. That is a Unity game that originally had issues with the XBO controller but the developers took the time to fix it. So it is possible to do.
What concerns me is this controller is along with Windows 10 being "bigged up" as being for gamers by Microsoft but it clearly has issues with a growing number of Unity Engine games. This is a hugely popular engine with indie devs and unless the devs actually report these issues to Microsoft and the Unity creators then I fear this problem is going to become more widespread as Windows 10 takes a larger share of the market.
I actually regret having got rid of my 360 controller because it at least worked with every game yet despite the XBO controller looking exactly the same it clearly does not work the same on a driver and engine level. It is frustrating to encounter so many games with issues, Hard West being yet another example as I found when I picked it up in the Steam Sale a few days ago.
Understandable but you really should be offering full support for both the older Xbox 360 *and* the newer Xbox One controller in my humble opinion, given how popular they both are. With Windows 10 and its Xbox One integration, the XBO controller is only going to become more popular over time and will eventually replace the 360 controller (it's only a matter of time before it is no longer made).
The issue here is that we have to create a custom controller profile ourselves. Setting it up correctly was a bit of a hassle which is why I shared the one I mapped. The Xbox One controller is supposed to work with all games supporting the 360 controller out of the box. That's what's so surprising and it's also what's grinding our gears.