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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
Tested Trine 2, Bastion and Eversion, gamepad does not work on any of them.
Investigating for a solution, suggestions are welcome ;)
Thinking to use PlayDeb (http://www.playdeb.net/updates/ubuntu/12.04/?q=qjoypad) which maps gamepad's buttons to keyboard keys. But I'd prefer having gamepad working as expect.
I think it's better if you report this on Steam bug tracker, here: https://github.com/ValveSoftware/steam-for-linux/issues
I'll def post something to github issues when I get all the details. But if it only supports 1 or 2 MS controllers at the moment they might not jump into it right away.
Here are my USB Adapter details:
usb 7-1: new low-speed USB device number 2 using uhci_hcd
usb 7-1: New USB device found, idVendor=0e8f, idProduct=0003
usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 7-1: Product: USB Joystick
usb 7-1: Manufacturer: GreenAsia Inc.
input: GreenAsia Inc. USB Joystick as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/input/input5
pantherlord 0003:0E8F:0003.0003: input: USB HID v1.10 Joystick [GreenAsia Inc. USB Joystick ] on usb-0000:00:1d.1-1/input0
pantherlord 0003:0E8F:0003.0003: Force feedback for PantherLord/GreenAsia devices by Anssi Hannula <anssi.hannula@gmail.com>
# jstest /dev/input/js0
Driver version is 2.1.0.
Joystick (GreenAsia Inc. USB Joystick ) has 7 axes (X, Y, Z, Rz, Hat0X, Hat0Y, (null))
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ...
Will report back if I find out anything else.
issue on GitHub : https://github.com/ValveSoftware/steam-for-linux/issues/2092
Adobe dropped flash support for Linux a while back so dont expect them to fix joystick support in their linux flash binary. Ever. Probably not for Mac either.
Srsly, ♥♥♥♥ Adobe.
Vitriol is mostly correct, and the solution provided will work. However, I believe it's incorrect that Steam is reading joystick input the "wrong way" or that they are "in-the-dark".
In general, there are two ways for a piece of software to access a gamepad on Linux: using the Input API (/dev/input/event*), or the Joystick API (/dev/input/js*). The Joystick API is the older API, and doesn't support some of the things that the Input API does (such as force feedback).
So, theoretically, they can both be used, but why use the older API when you can use the newer one? This is what Steam has decided to do.
The problem with this approach is that some Linux distros continue to provide the default security settings of the Input API (the /dev/input/event* files) so high that a user cannot access the file, therefore making it impossible for software like games or the steam client to access them. So long as the Linux distros continue to make the /dev/input/event* files only accessible via root, users will have issues getting the best out of their hardware.
So, yes, the resulting problem, as Vitriol points out, is one of file system permissions. Vitriol's solution basically makes all of your input devices user-readable, meaning any program run on your system can easily gain access to your keystrokes or other input devices. If you're playing on your gaming desktop, this probably isn't a big deal for you, so you can just use that solution. Otherwise, you can do the following to only make the controller available to non-root users (this worked for me on a Debian testing system, your results may vary). You can find more info on this blog post:
http://buzzdavidson.com/?p=45
1.) Plug in your controller
2.) Identify the input device your controller: you need to know which /dev/input/event* file is your controller. Probably the easiest way to do this is to do the following...
Here I have two controllers plugged in: a Microsoft X-Box and a Logitech Gamepad. The XBox Controllers points to js0 and event11, the logitech to js1 and event12. So, if I want to fix the XBox Controller, I need to remember event11 (/dev/input/event11).
3.) Make sure that your problem actually is the fact that the input system is using bad permissions. Try the following...
Of course, replace event11 with the event file you found in step 2. It will probably say "Permission denied". If it does, then yes, you have a permissions problem. Now try the following:
Then try pressing buttons on your gamepad. You should see the console scroll a bunch of gibberish. This is your gamepad working, but only for root. If these are your symptoms, then continue following these instructions for a fix.
4.) Gaining identifying attributes:
Now you need to find out information that you can give to the Linux system to identify this device whenever you plug it into my computer....
This runs two commands in one and returns a list of things that can identify your controller. Once again, replace event11 with your event. My results were as followed:
Specifically, I'm looking for something that I can use to identify this device, which I see at....
Since there's very little chance I'm ever going to plug a keyboard in that also has the name of "Microsoft X-Box 360 Pad", I can safely create a rule that says to look for this device and do something special with it.
5.) Now, I create a new file in /etc/udev/rules.d/99-joysticks.rules...
What this is saying is, "Whenever I detect that a device on the input system with the name 'Microsoft X-Box 360 pad' is connected, I want to make sure to set the file mode to 0666". Mode of 0666 means "rw-rw-rw-". In other words; read- and writeable to all users.
Now you can apply the rule so that it can occur on your already plugged in device...
Continue adding another line in the 99-joysticks.rules file for all your devices using the same steps above. If all goes well, your gamepads should be able to be tested without root required, which you can test with....
Install qjoypad.
Make a layout in qjoypad for it and correspond the keybind configuration in the game with it.
Start the game with this script:
Obviously, you could replace steam with any game/program you are ever having issues with. It does not ever actually fix the issue with a program, but it's a hell of a lot easier and much more convenient than trying to fight a program tooth and nail getting it to recognize a joystick.
This comment worked for me on Ubuntu 13.04. After going through it and restarting my computer, I launched steam big picture and found my controller (Microsoft original xbox controller S). I just needed to map buttons and it worked navigating menus. Launched a game (solar 2) and it earned me the last requirement for the steam hardware beta badge.
This enables the permissions until the device is unplugged or the computer is rebooted. It's not a permanent solution, but it gets the job done if you just want to get on with playing a game. >8)