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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
Edit:
Look into Joystick Gremlin. I use it a lot for my joystick setups in older games, or games that have poor out-of-the-box joystick support.
http://whitemagic.github.io/JoystickGremlin/
Honestly it has a lot to do with the way Microsoft implemented joystick support way back when. Joystick Gremlin gets around all the shenanigans by creating a virtual joystick, a piece of hardware that doesn't really exist, a kind of "phenomenological joystick" if I could coin that term, and allows you to define an arbitrary number of buttons, sliders, toggles, rotors, and axis to it. And then if you have multiple joysticks, throttles, foot pedals, button boxes, etc, you can pipe the output of all those devices, to individual events in the virtual joystick. This is beneficial for if you want to use multiple inputs, say a throttle and stick, in a game that only has the ability to recognize a single device at a time. You just tell the game to use the virtual joystick as your primary device, and route all your others through that. Also helps if for whatever reason, your old stick isn't being recognized by the game.
https://www.youtube.com/watch?v=jIAdeyY0IWI
This explains a lot.