安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
I'm about to contact the developers so we can work on a proper fix, but at this time, the only solution we have is to uninstall vJoy.
IF uninstallation of vJoy does not resolve the issue for you; please post your system and os specs.
How can you make it? It's not hard. Run console - type "cmd" into Start. And write:
So yeah. This game is unplayable with controller.
@boazlaurens You're the first case I'm aware of this happening on a mac. I'd be glad to work with you to try and resolve the issue. Are you moving left without the controller plugged in? if not, it could again be the calibration.
@Liko On Mac? Try rebinding the controls from the options menu.
Does the selection box move when the joystick is not plugged in?
I'm also using the same exact controller and get this issue. A disable gamepad function would be great so that we can assign the buttons to the keys instead. I really prefer playing platformers with a controller and would greatly appreciate this.
EDIT: i solved it, i went to >options>reset control bindings and now it works! :D
Sorry to say I don't play your game, but I have written a vJoy feeder application for rudder pedals recently and know why this happens and what to do about it.
I had exactly the same problem in ALL games that recognise the 1st Direct Input device on the development machine after using my rudder mapping program. My program takes x and y axis of a selected Direct Input device, and maps them to a centre resting single X-axis on vJoy Device #1. When terminated I simply relinquished the input and output devices, leaving the vJoy device axis centred, ie. half way up. This effect is persisted on the device, even following reboots.
To Fix, I simply added a call to the vJoy device ResetAll() in the close down code that unpresses all buttons, and sets all axes to 0. It might be possible for your application to do something similar before startup, to make sure any vJoy device axis are zero'd.
Hope this helps.
ps. I was actually looking for help with disappearing vJoy devices when I came here..