Instalar o Steam
Iniciar sessão
|
Idioma
简体中文 (Chinês Simplificado)
繁體中文 (Chinês Tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Checo)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol de Espanha)
Español-Latinoamérica (Espanhol da América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polaco)
Português (Brasil)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar problema de tradução
https://www.reddit.com/r/StarWarsSquadrons/comments/j3f31x/anyone_else_having_issues_with_massive_deadzone/
I did. Weird as this is, try navigating the binding screen using a different type of input. Like, if you were using the mouse, then try instead navigating it with a gamepad, or mapping navigation controls to the joystick and using those. I have no idea why this is so, but the game refused to recognize my left Crosswind rudder until I navigated that screen with an Xbox pad instead of the mouse. Likewise, it wouldn't recognize my VKB if I navigated the binding screen with the Xbox pad; I had to use the mouse.
This could very well be a coincidence, but PC games have had sillier quirks.
Here's what they posted in Discord:
*****************************
After a bit of testing I realized that this vjoy device Z axis didn't have the deadzone issue after remapping it to Pitch/Roll/Yaw.
I then used the VKB config to switch the X/Y axes on my Gladiator NXT with the Z/Rot Z axes bound to the throttle slider and twist. Keep X/Y active on a slider or function that you're not using, otherwise the game wont recognize your controller. It looks like the deadzone issue only affects the X/Y axes, but none of the other ones.
I've restarted the game a few times to make sure that this is persistent. Technically this should also work through joystick gremlin or any other software that lets you rebind the X/Y axes.
*****************************
So yeah, the game only has the deadzone bug with what it sees as the X and Y axes. So if you use some remapping software (Joystick gremlin/similar vJoy mapper, or your stick's first-party mapping software) to make the game think that your physical X/Y axes are actually some other axes, then there's no deadzone. The game thinks my physical X/Y are actually X-Rotation and Y-Rotation, and since the bug doesn't affect those axes, I'm now deadzone-free!
This is the most #pcgaming thing I've ever seen, hahahahahahahahaha.
Until you mash some buttons to make the game "switch" again to the joystick mode, and have you start to have controls using the joystick. Is it one of those cases?
Nope, it's a deadzone issue. Here's a reddit video showing it: https://streamable.com/nxp2jt
Fortunately, a buddy found a workaround, posted just above!
See a few posts above for a workaround. You'll have to save a new VKB profile and switch to it for this game, specifically, but at least it works!