You can check ProtonDB for specificerar games compatability. Most games from steam just install and run as usual. But other launchers and some games with anti-cheat can be a bit more wonky to get running or just dont work at all.

Personally WSL has always been riddled with issues for me. I mainly used it for dev things before I switched to linux entirely. Recently I came back to Windows to try some of AMDs new graphics driver features and decided to try out WSL 2. Hell, Windows fucks up so much basic shit in there, i couldnt even run ‘git init’ because some permission issue with drive mounting. Had to move my entire project to a separate drive just to make it work. The way Windows handles the filsystem, permissions and “cross-OS” functionality is so weird and always results in some issue, making the Linux experience feel significantly more wonky than it needs to be. Performance is also a pain, since i had to love my project to a disk that was not part of WSL reading and writing files in VS Code becomes significantly slower.

I have a pretty high end rig and even my PC runs slow when using WSL, its great to have an option for linux in windows but when a docker container or even just a VirtualBox machine performs better than WSL i have no fucking clue why youd use it.

Thanks for listening to my rant. Take it with a grain of salt ig, maybe im just incompetent and doing something very wrong.

This is very valid but in our case we dont really store any important data on the computer. We make digital timetable signs for bus stops and train stations, the computers we build and put inside are just a base image we flash onto the disk and set hostname and IP on. Then they all connect and set themselves up via our servers and pull any displayed data from our actual main servers.

In this case its sad that it didnt actually restart, that means our client has to drive out and deassemble the entire sign. But it seems to be a failing disk so it had to be replaced either way.

We did try that, it just have us Permission Denied

I would use the man pages but my working laptop uses Windows and since the system died i dont have any way to check them until I get home.

Thank you a lot for the answer though, that does explain a lot!

Pascal or camel case for code, snake case for files and screaming snake case for globals

Will update the original post but I solved it. Apparently there’s specific gamepad settings inside of Wootility under Settings > Gamepad. There you have to select what type of controller the software will emulate. I just took the recommended (Xbox Controller) and now it works as expected.

The keyboard itself is fine if I use regular mappings, however in the wootility software they provide (yes they have an official linux version) you can map controller inputs to your keys. So for example I can map (emulate) controller joystick left input to my A key to emulate the analog signal. These does not seem to register in-game. Other key inputs work fine.

Not related but I’ve had some dual booting issues aswell. Turns out that the drives mounted in Linux didn’t properly unmount on shutdown so when trying to access them on Windows they wouldn’t be accessible.

Just some info for anyone that might be having issues

This goes hard

What KDE/Kwin version do you use? Would be interesting to compare.

Edited the original post but might aswell comment it. I switched to GNOME (Wayland) and the FPS issue seems to be gone there. I ran the game with only the command line arguments “gamemoderun %command%” in steam and it seems to work properly. Very odd issue.

Launching it in GNOME (Wayland) seems to fix the issue. Very uncertain what this issue was but it seems to be related to KDE.

(Also I did not let the shaders compile, so not a shader issue)

Got gamescope working but the issue still persists. I’m gonna try launching in different DE aswell as letting shaders fully compile.

Good info, I will try this tomorrow and report back.

I had not seen this, but V-sync was off all the time :(

I’m on Wayland, so no X11 shenanigans going on here 😭

I removed all of my other arguments and tried to start with “gamescope -W 2560 -H 1440 -f %command%”, when I start the game the “Processing Vulkan Shaders” steam pop-up shows up, and when I click “Skip” (as I always do) it just disappears, no error or anything, the “Play” button on steam just goes back to green.

Update: This did not solve the problem :(

Monitor and game both running with 240hz set as refresh rate, game is also set to max fps at 360 but also have display refresh rate set to 240hz (yes, there were separate options for this)