Instale o Steam
iniciar sessão
|
idioma
简体中文 (Chinês simplificado)
繁體中文 (Chinês tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Tcheco)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol — Espanha)
Español-Latinoamérica (Espanhol — América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polonês)
Português (Portugal)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar um problema com a tradução
Your contribution will make this game's design will make it easier for people to have an engaging and appreciable experience.
We are happy to be of service.
That said, yes I think a sensitivity slider would fix the issue. The button mapping seemed to work fine until it was interfered with by a 3rd party's input. So leaving XPadder out of the equation would correct the backward controls.
Would you like to make a suggestion as how to tackle the issue? I can think of a few off the top of my head.
1: Include a camera sensitivity slider in the control config.
2: Have it to where the player can change the camera sensitivity real time using the 1234 keys on the keyboard.
The issue I'm having is the cursor/camera speed. It's hyperactive & there is no option to reduce sensitivity. I tried an XPadder remap & tweeking the sensitivity that way. However it seems the game overrides existing settings & resets them the way the game sees fit so the speed never changes. Also when using XPadder over top of the game the games controls appear to get confused with the XPadder's settings causing backwards controls. I assume this is due to the game always listening to the controller for input.