


Runs perfectly fine, but you need Proton to play with a controller.
Used a Switch Pro Controller, buttons randomly shuffled or stopped working. My assumption is that it doesn't work well in the Native version. (Deduced from trial and error)

Was even able to install mods using Lumafly without issue as well, for those who are interested
Switch 1 pro controller was acting weird. switching to experimental fixed it

При нативном запуске задержки ввода, пропуски и отсутствие вибрации.
При работе нативно происходят дропы FPS.
Играйте через Proton, так не будет проблем с производительностью, геймпадом и вводом.

SDL_DYNAMIC_API=/usr/lib/libSDL2-2.0.so.0
Fixed by setting SDL_DYNAMIC_API

Controller not mapping properly on native version, switching to proton works perfectly
Issues with cloud saves
Worked fine with some controller issues, switching to proton runs perfectly with no issues
Works well out of the box.
Worked perfectly out of the box.

Works great without tweaks
Cloud Sync doesn't work

When running natively the mapping on my Xbox Series controller gets scrambled (e.g. pause was mapped to RB). Running the game under Proton is a workaround.

DRI_PRIME=1 %command%
Steam input was turning on and off for my Switch Pro Controller
Couldn't sync, maybe because my save data was created on Windows?
All problems listed are present with the native Linux version. Once I switched to Proton, the game played flawlessly. It instantly synced and loaded my save data and Steam Input started working with my Switch Pro controller.

Changed from using native Steam runtime to Proton.
Before switching to Proton, my Wireless Horipad for Steam had its mappings completely wrong. For example, the right stick's vertical axis and the right trigger were swapped, and the face buttons, bumpers, select and start were shuffled. Switching to Proton completely fixed this.

Runs straight out of the box
No issues was detected, and I was able to finish it will all the DLCs as well
SDL_DYNAMIC_API=/home/greylily/.steam/root/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 %command%
Using a dualsense controller you have issues with some of the buttons. The options and share buttons (start and select) do nothing. The inventory and super dash power are both mapped to left trigger. The dash and pause menu are both mapped to right trigger. Remapping controls in game does not work. And trying to remap controls via steam does not fix these issues. You have to use a special launch option to fix the controls. Works great other than that.

Had major button mapping issues and slight input lag when playing natively with a Pro Controller. Steam Input would conflict with Linux's native controller input mapping. Fixed by running the game through Proton GE and just using Steam Input.
Game runs great, just a few janky Pro Controller issues, but what's new. Mods also work excellently.

Hollow Knight runs well on PCs that do not have a dual GPU setup
Sometimes, the game stutters on higher resolutions (2560p is fine, anything above that can cause unexpected lagging in graphically intense areas, but other than that, there are no issues). I have not tested this on Windows, but guess that there would be worse problems.
The game runs exceptionally fine on hardware that has no "dual GPU / bumblebee / prime" components. This was mainly an issue on older versions of openSUSE and still persists to this day on some graphic chips, so be sure to have your drivers properly installed.
Other than having issues with offloading to a dedicated GPU on my laptop, the game runs very fine, both on PC and on Steam Deck.

With vulkan backend, screen recording was stained green

Running with proton, this game is good and stable
Very good performance in vanilla Debian

Даже контроллер Xbox работает без проблем. Всё идеально.

At first, my controller wasn't working properly. Switching to Proton Hotfix solves this issue
Native Linux Runtime does not bode well with DualSense
Linux Runtime seems to not click well with DualSense, I recommend using a version of Proton if anything like this happens to you. Played and it ran perfectly from then on

SDL_GAMECONTROLLERCONFIG="050000004c050000e60c000000810000,Sony DualSense ,a:b0,b:b1,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b10,leftshoulder:b4,leftstick:b11,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b12,righttrigger:a5,rightx:a3,righty:a4,start:b9,x:b3,y:b2,platform:Linux," %command%
Using PS5 controller inputs were incorrect, had to use the following launch option:
SDL_GAMECONTROLLERCONFIG="050000004c050000e60c000000810000,Sony DualSense ,a:b0,b:b1,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b10,leftshoulder:b4,leftstick:b11,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b12,righttrigger:a5,rightx:a3,righty:a4,start:b9,x:b3,y:b2,platform:Linux," %command%
Only issue was with the PS5 controller and the launch option resolved it.

Runs perfectly fine on steam deck, played a big part of this game on Linux.
no issues at all 10/10 out of the box

Had to disable steam input.
Sometimes attacks were voided on switch pro controller.
Disabling steam input fixed it.

controller mappings didn't work properly with native play, but with proton it works as normal

The native version of Unity on Linux is known to have controller issues. Often times the game wouldn't recognize my controller, have input lag, or only recognize one input at a time. I fixed this issue by enabling steam input for my controller (strange). If you don't want to do this though, I recommend you run the game through Proton.
Utterly flawless experience.

PROTON_USE_WINED3D=1 %command%
La version que se corre de forma nativa presenta errores en el rendimiento del mismo, las frames se congelan a cada rato, sin enbargo, lanzado con proton no pasa esto

Runs great with Proton
Native version had some graphical glitches and would run my computer a lot hotter. With Proton it ran smoothly and cooly
If you connect your controller after the game was opened it won't connect, you have to restart the game with it connected
Zikway Gamepad HID (GameSir t4n-lite)
Custom HID gamepads are bugged, there seems to be no way of overriding this even when launched from steam as a custom game.

Flawless
This one works great without any tinkering.

Use the Proton version. I had issues with the button mapping on my XBOX controller.
I did not have this issue with the native version on the Steam Deck

Al instalarlo de forma nativa no detectaba la vibración del mando, pero al cambiarlo a Proton Experimental la vibracion funcionaba perfectamente. (Machenike G5 Pro V2)
Si vas a usar algun mando y quieres disfrutar de todas sus caracteristicas te recomiendo cambiar la configuración a Proton Experimental.

-vulkan
Slight window tearing is present that the native version does not have
Just use proton, native port is not that well made

%command% -vulkan
On the native Linux version, there's crazy input lag, no rumble, and the dash often just... doesn't work? It works beautifully on Proton, though.
Use Proton. I'm afraid the native Linux version just isn't that good for controllers, and probably has other bugs I'm not aware of as well.