安装 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.