

Running perfectly!

Other than having to use the touchscreen for the launch window, the entire game plays without any issues
you can set the TDP to 5w for an imporved battery life without sacrificing any performance
You need to click "play" on a launch window. just simply tap the button with your finger, using the touchscreen.
It occasionaly crashed but the crashes never happened in a bad spot for me, and it wasnt that frequent so it was ok

Perfect using arch linux
if you want to use this kind of games in arch linux, you won't have any problems

Runs as it's on windows, but you can't acess to the saves you had on Windows
I don't have saves from Windows

Game behaves erratically (extreme lights flashing, completely unplayable) IF there is any FPS Counter software enabled on the system (even Steam's own FPS Counter). After disabling it, the game plays as normal.
Awesome game

Native support and works right out of the box.
Hotline Miami works right out of the box because it has native support. In a worse scenario, you can run the Windows version with Proton or Wine, but I haven't dealt with that issue.

The windows build worked for me with no problems with proton, the native build was missing a bunch of libraries.

capped at 60 Hz and 6W TDP but probably not needed
needed to use touchscreen or Steam+rpad to get through the games intial config screen
Works great natively out of the box.

Works almost perfectly, the only exception is that there is an occasional lighting bug which causes wooden tables to flicker. Very strange, and not really of consequence.

works perfectly fine, recommended for new users.
Works great. Native support.

To get past the graphics options launcher I had to hold the steam button and use the mouse to select Start
The deafult controller layout for thsi game simply doesn't work. Currently need to download a community layout or bind your own controls.
Works great both with Proton and Natively without any problems

I like hurting people.
werks

Feels great on the deck

Your controllers right stick will not be detected, you need to turn off steam input and use the Built in controller support
You Need to switch to Experimental otherwise the game will not register your right stick input correctly, then you need go disable steam input. Finally a start up window will appear that you need to either use touchscreen or an external mouse to get past only then can you begin playing.
work out of the box
Runs perfectly

Excellent native version
Your progress will not carry over if you're going from from Windows to Linux
Works perfectly

Works great
No tinkering needed

До ввімкнення proton правий стік замість того щоб повертати камеру, працював як кнопка атака. Після ввімкнення proton автоматично ввімкнулось введення Steam, через що гра взагалі не реагувала на геймпад. Після вимкнення введення Steam все запрацювало без проблем.
Easy, worked perfectly
using the native build, the game ran at 1/3 the framerate. using proton fixes this

Runs great. Saves from Windows ported well
It's a 2D Game it will run

Works flawlessly on the steam deck. Before the game starts there's a window that lets you pick a resolution, for that you might need to use the touch screen on default config.
The game works out of the box with no tweaks or changes.

-skip
adding -skip to Steam launch parameters skips the initial launch window (you have to clic with the finger on the screen otherwise)
disabled the Steam deck native fps cap to reduce input lag, game stayed at stable 60 anyway.

Need to get past launcher via touchscreen or Steam + Trackpad
As of Mesa 22.3 you need to add the provided launch parameter or the game will stay black (you can hear the audio but no picture)
mesa_glthread=false %command%
I had to use a mouse in order to get pass the initial pick a resolution window.
I had this weird issue were after putting the deck to sleep and going back to the game the buttons on my controller (8BitDO Pro 2) were swapped. The A button swapped to the start button and such. However in order to fix this I had to restart my deck everytime.

env QT_QPA_PLATFORM=xcb %command%
If you're not running KDE-wayland or didn't enable wayland for QT apps yourself through env. vars you won't even need to use provided launch options