[Linux] Grabs my keyboard and mouse but does nothing with it.

[Bepis]

Can't move, can't do anything. I'm forced to go to a tty to kill the game because the damn thing grabs all my input devices yet they don't seem to work. Tried disconnecting my joystick and tried disabling Steam overlay. Nothing.

Don't you guys test your games before shipping?

[James Lee Stool]

I can confirm.

But in my case - I can't even press 'yes' or 'no' at the start of the game, when it asks about removing the violent scenes.

I also don't have sound in game.
Well, the sound problem can be solved with pavucontrol, by setting the audio source to another device, but the final result of it is glitchy sound.



That's really dissapointing.

[Matoking]

Having the same problem. I can open and hide the Steam overlay using Shift+Tab, use the menu and see the mouse when Steam overlay is open, until a short time in when the game stops responding to any key presses, or in one case, does work but with delay (I have to keep a button pressed for one second before the main menu responds in any way).


It also seems to make the desktop itself behave oddly, since the mouse seems to disappear and the system doesn't respond to keyboard presses as it should. When I try to kill the game using Alt+F4 it also seems to not do anything for a good 20 seconds or so.

[Achille Laburne]

Keyboard doesn't work for the move, i change the controls but nothing....

[Bepis]

Messaggio originale di Matoking:

or in one case, does work but with delay (I have to keep a button pressed for one second before the main menu responds in any way).

Can confirm.

Testing with Xbox 360 controller and game seems to work fine with it. But I didn't preorder to play Hotline Miami with a ♥♥♥♥♥♥♥ joystick. What's up?

[Teal]

Same here.

At first input works, but very briefly. After that, the game proceeds to capture it all, but ignore it.

When in this state, the game also ignores SIGTERM and can only be disposed of via SIGKILL or such.

[TFJ]

Same issue here, also running on Linux. Joystick seems to work fine, but I want to play with keyboard + mouse.

[James Lee Stool]

Messaggio originale di Teal:

Same here.

At first input works, but very briefly. After that, the game proceeds to capture it all, but ignore it.

Can confirm that too.

I've pugged my SVEN X-Pad in and then controls were working, but...mouse was acting like a controller's stick. That's strange.

Then I've unplugged controller and faced the first problem - controls won't work.



But!

I've figured out how to launch it with sound(for those, who use pulseaudio) - just do padsp ./HotlineMiami2 in game's folder.

[Bepis]

Messaggio originale di Восьмибитный Дед:

Messaggio originale di Teal:

Same here.

At first input works, but very briefly. After that, the game proceeds to capture it all, but ignore it.

Can confirm that too.

I've pugged my SVEN X-Pad in and then controls were working, but...mouse was acting like a controller's stick. That's strange.

Then I've unplugged controller and faced the first problem - controls won't work.



But!

I've figured out how to launch it with sound(for those, who use pulseaudio) - just do padsp ./HotlineMiami2 in game's folder.

I have PulseAudio and the pulseaudio-alsa package (running Arch Linux) and audio runs out of the box here.

[ChaZcaTriX]

Mint 17.1 Cinnamon (Ubuntu 14.04 equivalent), same here.


Even when the game for whatever reason runs fine - the cursor is completely grabbed by the game, and tools like xkill fail to find it.

[James Lee Stool]

Dunno why it(I mean, sound) don't want to work when launching through steam.

[ChaZcaTriX]

Just a random guess: do you guys use mice/keyboards that manifest as multiple devices in xinput --list?

[Bullace]

Messaggio originale di Chin Geese Khan:

Just a random guess: do you guys use mice/keyboards that manifest as multiple devices in xinput --list?

Yup

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech G9x Laser Mouse                	id=8	[slave  pointer  (2)]
⎜   ↳ Logitech G9x Laser Mouse                	id=9	[slave  pointer  (2)]
⎜   ↳ Logitech Logitech Illuminated Keyboard  	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Logitech Logitech Illuminated Keyboard  	id=10	[slave  keyboard (3)]

[Bepis]

Messaggio originale di Chin Geese Khan:

Just a random guess: do you guys use mice/keyboards that manifest as multiple devices in xinput --list?

Yes. Please don't tell me the devs pick devices manually instead of defaulting to master device.

[James Lee Stool]

Well, um...

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech Unifying Device. Wireless PID:101b	id=8	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Eee PC WMI hotkeys                      	id=9	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=10	[slave  keyboard (3)]
    ↳ Logitech K810                           	id=11	[slave  keyboard (3)]

[igi-111]

Having the same problem
I wonder what they used to catch input.
Anyway here's my xinput --list ouput

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech G500                           	id=8	[slave  pointer  (2)]
⎜   ↳ Logitech G500                           	id=9	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=10	[slave  keyboard (3)]