Thank you for helping to keep GamingOnLinux civil and safe!
Please tell us why you're reporting this content. Please note we store your IP address for all reports to help prevent spam and abuse. You can also email any complaints to: [email protected].
- Survive an elevator trying to eat you in co-op horror KLETKA when it releases February 19
- Draft code submitted to KDE Plasma turns it into a full VR desktop
- Proton Experimental brings updates for MonoGame, Rockstar Launcher and more
- Valve tweak Steam AI disclosure form for developers to clarify it's for content consumed by players
- No Rest for the Wicked co-op update lands on January 22 and it hit a big sales milestone
- > See more over 30 days here
- Casual/Social places for developer chatter
- simplyseven - Will you buy the new Steam Frame?
- eev - One-time logout
- Liam Dawe - Away later this week...
- Liam Dawe - Weekend Players' Club 2026-01-16
- grigi - See more posts
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
The Unity Vulkan code is simply broken and leads to something like this on my and other systems. This is my system, I made the screenshot myself:
https://steamcommunity.com/sharedfiles/filedetails/?id=3547585264 [External Link]
The error has existed for years now.
https://www.reddit.com/r/HollowKnight/comments/wg2f8r/graphics_issue_on_steam_deck [External Link]
I have very little hope that it will be fixed. Hollow Knight is my favorite game, and I've been playing it for a long time. Until around 2021, I had hardly any problems with the Linux build. But now I'm having a lot. It all started when they switched the game to Vulkan. Maybe Unity would be better off using DXVK for its Vulkan path and basing the Linux build on the Windows version.
That definitely means something to me. Even so: We don't need to view our system through rose-tinted glasses. Linux has strengths and weaknesses. Backward compatibility isn't one of its strengths. Even glibc likes to break userland. The typical scenarios in the OSS space are covered. If something breaks, it's quickly repaired. But when it comes to closed sources games, nobody cares.
Thanks for the tip. I'll keep your page in mind.
But: You can see for yourself that you fix it yourself.
As a technically inclined person, I think that's great. But as a gamer, I'd probably sit in front of my PS4 at some point. Hollow Knight is, for me, an artistic experience. So when I notice reflections in the Linux build of Silksong where there shouldn’t be any, the enjoyment is gone.
I simply don't trust native Linux builds from Team Cherry anymore because this developer obviously don't really test them. But I'm still a big Team Cherry fan. Am I crazy? Maybe. These people earn millions but apparently it's not enough for a proper Linux build.
With a native Linux build, I'm dependent on the game's developer. With Proton, I'm usually dependent on Valve and the community. Many game developers are simply terrible at their Linux builds. They just click the Linux button in their engine without adequately testing the resulting output. That's my personal impression.
Proton is the solution for me in this and other cases. Especially since I simply couldn't play some of my favorite games without Proton. Elite: Dangerous.
I hope you can understand me. I think I do the same in reverse.