Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
kinda requesting for them to make a patch to give us accessablilty to chaning camera options. Or to fix the bug altogether.
Edit: somone said somethinng bout xinput being the issue
Let me guess? The one detected and automapped correctly is a genuine wired X360 controller. The one that's failing is a knock-off?
This game is likely, exactly like all other Koei PC ports, not using XInput but the older DirectInput standard. And while XInput has fixed physical buttons mapping to fixed logical representations in code, DirectInput makes absolutely no such guarantee and can pretty much have its buttons mapped however the heck it pleases.
Knock-off controllers are very likely to have a different internal mapping for DirectInput.
On top of that, iirc, Koei was caught doing very very naughty things in their past ports with regards to setting the default button mappings. I think they were trying to detect genuine X360 or XBOne controllers by using their device name and /or device hardware UUID.
The former is flaky with regards to localized drivers and localized device names. The latter is flaky with, e.g., wireless X360 controllers and non-genuine receivers. Non-genuine receivers carry a different UUID from the official one and would cause code that sniffs for them to determine connected genuine X360 controllers (with the proper DirectInput hardware mapping) to be detected as a non-genuine.
(It's a bloody mess...)
Oddly enough, the one that's not working right is the one that works correctly on DW8XLCE, DW8E, and even Bladestorm Nightmare (as much as a colossal screwup that one was at launch, controls seemed to be working on that one).
I've went ahead and linked this thread to KoeiTecmoUS over on twitter. For their reference:
Controller (XBOX 360 For Windows) [which appears to be a first-party wired controller] works correctly in SW4-II, haven't tested it on prior games yet.
Controller (Afterglow Gamepad for Xbox 360) [3rd-party wired Xbox 360 controller] works correctly in DW8XLCE, DW8E, and Bladestorm Nightmare but suffers from wonky button mapping in menus and has horizontal camera control mapped to Z-axis (LT and RT) and presumably vertical camera controls mapped to ZR-axis (which doesn't exist on the controller).
The only remedy to make it "work" like an XBOX 360 controller is search for the drivers dated from 2014. This will revert the Z-Axis for LT and RT back to a single axis, but you will sacrifice the use of the XBOX button if you use that for accessing MS recording function. If the game still has issues even with the 2014 drivers then it is the publisher/developers that need to implement it correctly.
I don't have the time currently to try this out, but if someone does can they report back? This is the only thing keeping me from playing it more, so if this ends up working, I'll be very happy with it.