FEZ

FEZ

Zobrazit statistiky:
Key press stuck going left error (Linux)
I'm playing the Linux version of this game (Ubuntu), and when I start the game, enter the current level, the Fez guy immediately jumps off of the cliff.

After retarting the PC with *all extra periphals unplugged* (leaving only mouse and keyboard), it still does this. It's acting like there is a key press making the Fez guy go left no matter what keys I press. Playing with keyboard and/or game pad does this.

confirmed nothing is pressing any keys. No other games under Steam have this issue. Could this be a bug? When I went into the controls area, same issue when highlighting the options for movement.
Naposledy upravil IronSpanking1; 8. dub. 2014 v 17.34
< >
Zobrazeno 17 z 7 komentářů
I just installed SteamWorld Dig on Linux (Ubuntu 14.04) and I have this exact same issue. When I start the game, it infinitely scrolls at the options menu. When I use my mouse to try and overcome the scrolling between menu items to start a game, my character goes to the far left of the screen and I can't interrupt this movement. I've restarted the game a number of times and I can't see why or what is causing the directional input.
For me this has been resolved with the last Fez update, no more issues for me.
Good to know IronSpanking1 - I haven't seen an update of SW Dig so I guess I'll just have to wait to be able to enjoy this game on Linux.
Dex 13. čvc. 2014 v 6.21 
Some keyboards get mistaken for joysticks and things start acting weird. Can you post the output of:
cat /proc/bus/input/devices

If you still have the issue that is
Naposledy upravil Dex; 13. čvc. 2014 v 10.02
I have the same issue. This seems to be a rather recent issue as I could play fez correctly when I bought it on Humble Bundle. For me this has not been fixed by the recent update to 1.11.
Thats whats fez says:
Controller 0, Microsoft Wired Keyboard 600, will use generic MonoGameJoystick support.

from /proc/bus/input/devices

I: Bus=0003 Vendor=045e Product=0750 Version=0111
N: Name="Microsoft Wired Keyboard 600"
P: Phys=usb-0000:00:16.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:16.0/usb7/7-1/7-1:1.0/0003:045E:0750.0001/input/input2
U: Uniq=
H: Handlers=kbd event2
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=045e Product=0750 Version=0111
N: Name="Microsoft Wired Keyboard 600"
P: Phys=usb-0000:00:16.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:16.0/usb7/7-1/7-1:1.1/0003:045E:0750.0002/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=10001f
B: KEY=3007f 0 0 4c3ffff17aff32d bf54445600000000 c00000000000001 130f938b17c007 ffff7bfad951dfff febeffdfffefffff fffffffffffffffe
B: REL=40
B: ABS=ffffff01000701ff
B: MSC=10
Hi, try putting the following line in "/etc/udev/rules.d/99-joystick.rules". (You may have to create the file).

ATTRS{name}=="Microsoft Wired Keyboard 600", ENV{ID_INPUT_JOYSTICK}:="0"

Then execute these:
sudo udevadm control --reload-rules
and:
sudo udevadm trigger
this works but is of course only a workaround to the real issue of udev reporting this keyboard as joystick.
Thanks very much
< >
Zobrazeno 17 z 7 komentářů
Na stránku: 1530 50

Datum zveřejnění: 8. dub. 2014 v 17.34
Počet příspěvků: 7