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
Only thing lacking (last time I checked, which was in 1.03) is the camera being able to be rotated with the right analog stick (was in theory implemented in 1.03, but it didn't work for me), and the rest is... Just like how the DC version works with the DC controller. You shouldn't blame the devs or the +10-year old game for not being miraculously up to date on the controls to nowadays' standards.
This is why developers get away with this. Customers don't realize they're being hoodwinked.
And the funny thing is, it's actually LESS work for the developer to target xinput (the API) than it is to target the X360 gamepad. This mistake just shows their inexperience with the API.
But no, it's not proper xinput support, despite your brief experience with one controller.
OP still hasn't said what his problem with the controllers is.
You're missing the point of the thread.
Camera: left and right bumper
Everything else works too.
The game was designed with the X360 pad. You won't have issues with that. It's other Input controllers that have issues because they aren't always detected as X360 gamepads. With proper XInput support, X360 gamepad detection isn't needed and these controllers just work.
I'm sincerely glad that it works for you. I've heard mixed things on the F310/710/Sabertooth controllers. A proper XInput implementations would remove the issues being experienced by some.
I've sent you requests for this before. What I've gotten back from GungHo shows a lack of fundamental understanding in just how XInput works. I've tested with numerous controllers (Xbox 360, Xbox One, Logitech F310, Logitech F710, Razer Sabertooth, and Nvidia Shield local USB and GameStream). Proper Xinput support means that you don't have to select the gamepad in the settings, and all of the above gamepads work. GungHo makes the user select the gamepad in the settings simply because GungHo doesn't understand basic Xinput implementation. As such, anything outside of the Xbox 360 gamepad, even if Xinput capable, is a gamble (some work, some don't).
Microsoft has a good writeup on the basics and includes some sample code. Please pass this along to the development team:
https://msdn.microsoft.com/en-us/library/windows/desktop/ee417001(v=vs.85).aspx
The Xbox 360 gamepad has become the most common PC gamepad over the years, so kudos for at least ensuring that works. But had you guys used a proper XInput implementation, it would have worked anyway, and other gamepads as listed above would work.
Got it.
Having you uncheck a box to make the camera not spin incessantly in Windows 10 when using an Xbox One controller is not proper implementation.
Proper Xinput support would pretty much solve every control related issue in the game so far.
And you are actually able to use some controllers that you own (or rather, you were back when you still owned the game). This is certainly valid feedback, and I'll be sure to pass it along to the team. I can't guarantee any updates based on this, but we'll certainly keep everyone informed.