安裝 Steam
登入
|
語言
簡體中文
日本語(日文)
한국어(韓文)
ไทย(泰文)
Български(保加利亞文)
Čeština(捷克文)
Dansk(丹麥文)
Deutsch(德文)
English(英文)
Español - España(西班牙文 - 西班牙)
Español - Latinoamérica(西班牙文 - 拉丁美洲)
Ελληνικά(希臘文)
Français(法文)
Italiano(義大利文)
Bahasa Indonesia(印尼語)
Magyar(匈牙利文)
Nederlands(荷蘭文)
Norsk(挪威文)
Polski(波蘭文)
Português(葡萄牙文 - 葡萄牙)
Português - Brasil(葡萄牙文 - 巴西)
Română(羅馬尼亞文)
Русский(俄文)
Suomi(芬蘭文)
Svenska(瑞典文)
Türkçe(土耳其文)
tiếng Việt(越南文)
Українська(烏克蘭文)
回報翻譯問題
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.