Latest Comments by TheSHEEEP
Help more get noticed with the Game Devs of Color Support Bundle on itch.io
22 Aug 2025 at 9:06 am UTC Likes: 3
I understand the goal is to combat racism and honestly, who wouldn't be on board with that*.
But events and actions such as these - even if they put a positive spin on it - only cement skin color as a factor of otherness, something to stick out and notice, to look at and gawk, to pity or celebrate. I fully agree that is counterproductive.
Meaning well and doing well are not the same thing.
It is also wholly irrelevant in game development.
Nobody* would avoid buying a game based on the skin color of the dev (who would even check for that in the first place?!).
Now, cultures on the other hand, I get.
African devs, Ukrainian devs, etc. - culture can have a strong influence on the game, so categorizing in that regard makes sense.
But skin color is not a culture. Other than for public social posturing, I really do not see the point.
Also, if I was of color, I'd sure as hell not want my game to sell because someone pitied me for my skin color, or wanted to flaunt their social stance with me - I'd much rather the game sold because people liked the game.
*yes, I know, there's always someone. But that someone is so statistically marginal that it doesn't matter.
22 Aug 2025 at 9:06 am UTC Likes: 3
A great step toward eliminating racism would be to eliminate the thought of distinguishing people by the color of their skin. By promoting things, for good or bad, based solely on the skin is making a step backward in my humble opinion.Amen to that.
I understand the goal is to combat racism and honestly, who wouldn't be on board with that*.
But events and actions such as these - even if they put a positive spin on it - only cement skin color as a factor of otherness, something to stick out and notice, to look at and gawk, to pity or celebrate. I fully agree that is counterproductive.
Meaning well and doing well are not the same thing.
It is also wholly irrelevant in game development.
Nobody* would avoid buying a game based on the skin color of the dev (who would even check for that in the first place?!).
Now, cultures on the other hand, I get.
African devs, Ukrainian devs, etc. - culture can have a strong influence on the game, so categorizing in that regard makes sense.
But skin color is not a culture. Other than for public social posturing, I really do not see the point.
Also, if I was of color, I'd sure as hell not want my game to sell because someone pitied me for my skin color, or wanted to flaunt their social stance with me - I'd much rather the game sold because people liked the game.
*yes, I know, there's always someone. But that someone is so statistically marginal that it doesn't matter.
POSTAL 2 Redux has launched on Kickstarter
13 Aug 2025 at 5:58 am UTC Likes: 1
13 Aug 2025 at 5:58 am UTC Likes: 1
Hmmmm, with how badly Postal 4 went, I'm not sure what to think about this.
Two years later (or more?) and that game is still barely playable.
I am just not sure I trust these guys doing it better in a remake of Postal 2.
Two years later (or more?) and that game is still barely playable.
I am just not sure I trust these guys doing it better in a remake of Postal 2.
Portal: Revolution drops Native Linux support to focus on Proton
9 Aug 2025 at 1:59 pm UTC Likes: 1
For obvious reasons (and as I'm pretty sure I wrote above), MP games are exempt from this - they would run just fine, if the player wasn't flagged as cheater.
I did comment under the full assumption that that is the case - because, well, that's what it almost always is.
Oh! I do remember a crash now that I had under Proton when changing certain graphical settings in a game, maybe a year or two ago, which didn't happen under Windows.
However - that crash was unrelated to Proton, it was (IIRC) some sequence of AMD GPU calls (on Linux only) that would cause a crash no matter what tried to execute them. It was just through Proton and that game that I noticed - others had the same issue coming from other sources.
Nothing the dev could've done about it, either.
So yes, there was such a bug that did not happen under Windows. But it didn't affect my ability to play so I quickly forgot about it and don't really consider it important.
9 Aug 2025 at 1:59 pm UTC Likes: 1
https://www.gamingonlinux.com/2025/08/farlight-84-is-now-broken-on-linux-steamos-steam-deck/That's a multiplayer game.
(You even commented on the game not running before writing above comment...)
For obvious reasons (and as I'm pretty sure I wrote above), MP games are exempt from this - they would run just fine, if the player wasn't flagged as cheater.
I did comment under the full assumption that that is the case - because, well, that's what it almost always is.
Oh! I do remember a crash now that I had under Proton when changing certain graphical settings in a game, maybe a year or two ago, which didn't happen under Windows.
However - that crash was unrelated to Proton, it was (IIRC) some sequence of AMD GPU calls (on Linux only) that would cause a crash no matter what tried to execute them. It was just through Proton and that game that I noticed - others had the same issue coming from other sources.
Nothing the dev could've done about it, either.
So yes, there was such a bug that did not happen under Windows. But it didn't affect my ability to play so I quickly forgot about it and don't really consider it important.
Portal: Revolution drops Native Linux support to focus on Proton
9 Aug 2025 at 5:40 am UTC
But I cannot even remember the last time Proton was not able to run a game. It must've been years ago.
For a while I checked ProtonDB before buying a game - I don't even do that anymore.
Besides, plenty devs officially support Proton at this point - of course people then expect it to work, just like they would with a native port.
At this point in time (with the exception of MP and VR games), Proton is very much a "it just works" thing. And widely perceived as that as well. You are honestly the first person I see viewing it so negatively.
And I talk to lots of Linux folk, and even more to gamers outside the Linux sphere (usually talking about the OS itself), all of which very much seem to think they could run their games very well on Linux (and they expect occasional fiddling), but they are intimidated by the OS itself.
You are really allowing your own exceptional experience to cloud your judgement of what most people see - for that, a look at ProtonDB reports is more than enough. Way over 90% silver+ for reported games puts failure outside of a "normal parameter" with Proton at this point.
You can find plenty of bug reports of people running a game through Proton on Steam forums. Most of which of course not related to Proton.
But in the past, for example at least until Proton got its video support fixed, you could see a lot of issues raised ala "game works fine through Proton, but videos don't play" (remember that "TV test screen" thing?). Usually devs reacted to it, pretty much always others, with a variety of end results.
But it did get reported - official support or not.
If you are specifically talking about some dev-specific bug report channel, then yeah, you are probably right - but it's not like those are ever used by most people to begin with.
The vast majority of users, as in 90+%, do not ever use bug reporting features or "proper" channels (and I can tell you that from decades developing user-facing software) - and I'd wager gamers do it even less.
And again, lots of official Proton (often in the form of Steam Deck) support by now.
Then, it also depends on which dev you are talking about.
There is the Proton bug tracker, the Github one - obviously most people will never have a Github account, but considering that (and likely due to the higher amount of techies among Linux users) the amount of reports there are surprisingly high.
So, one could argue those very much report to the devs - the devs of Proton.
If some Proton-related bug is more likely to be fixed by the game dev or the Proton dev depends on the case.
Doesn't matter if anyone thinks it is "reasonable" or "plausible" - we are long past the times where one could expect people to behave in those categories, especially online.
If you think people wouldn't complain to a developer because something is not officially supported, then you live in extreme contrast to reality.
9 Aug 2025 at 5:40 am UTC
On the question of how well Proton works vs. native, the thing about some of your points is that people expect Proton not to work. I mean, yeah, they figure it will work most of the time, but failure is part of the normal parameters of using a thing like Proton;Maybe initially, when it all started out?
But I cannot even remember the last time Proton was not able to run a game. It must've been years ago.
For a while I checked ProtonDB before buying a game - I don't even do that anymore.
Besides, plenty devs officially support Proton at this point - of course people then expect it to work, just like they would with a native port.
At this point in time (with the exception of MP and VR games), Proton is very much a "it just works" thing. And widely perceived as that as well. You are honestly the first person I see viewing it so negatively.
And I talk to lots of Linux folk, and even more to gamers outside the Linux sphere (usually talking about the OS itself), all of which very much seem to think they could run their games very well on Linux (and they expect occasional fiddling), but they are intimidated by the OS itself.
You are really allowing your own exceptional experience to cloud your judgement of what most people see - for that, a look at ProtonDB reports is more than enough. Way over 90% silver+ for reported games puts failure outside of a "normal parameter" with Proton at this point.
Nobody reports it to the devs when they try a Windows game in Proton and it doesn't work; they know it's not supported.That depends a bit on what your definition of "reporting to devs" is.
You can find plenty of bug reports of people running a game through Proton on Steam forums. Most of which of course not related to Proton.
But in the past, for example at least until Proton got its video support fixed, you could see a lot of issues raised ala "game works fine through Proton, but videos don't play" (remember that "TV test screen" thing?). Usually devs reacted to it, pretty much always others, with a variety of end results.
But it did get reported - official support or not.
If you are specifically talking about some dev-specific bug report channel, then yeah, you are probably right - but it's not like those are ever used by most people to begin with.
The vast majority of users, as in 90+%, do not ever use bug reporting features or "proper" channels (and I can tell you that from decades developing user-facing software) - and I'd wager gamers do it even less.
And again, lots of official Proton (often in the form of Steam Deck) support by now.
Then, it also depends on which dev you are talking about.
There is the Proton bug tracker, the Github one - obviously most people will never have a Github account, but considering that (and likely due to the higher amount of techies among Linux users) the amount of reports there are surprisingly high.
So, one could argue those very much report to the devs - the devs of Proton.
If some Proton-related bug is more likely to be fixed by the game dev or the Proton dev depends on the case.
It's not a symmetrical thing when it comes to how and whether people complain,Oh, man, people complain. :grin::grin::grin::grin::grin:
Doesn't matter if anyone thinks it is "reasonable" or "plausible" - we are long past the times where one could expect people to behave in those categories, especially online.
If you think people wouldn't complain to a developer because something is not officially supported, then you live in extreme contrast to reality.
Farlight 84 is now broken on Linux, SteamOS / Steam Deck
8 Aug 2025 at 6:15 am UTC Likes: 2
I've seen some reports of developers (not necessarily game devs, but any coding) who are running some WSL ( Windows Subsystem for Linux ) for development - and somehow some of that running while a game was running triggered some anti cheat systems to flag them.
So even Windows people just running some Linux stuff for completely unrelated reasons get hit by this nonsense...
This will only stop if the share increases to something like 5-10%.
Or whatever number is needed for publishers to no longer outright ignore a chunk of their customers.
8 Aug 2025 at 6:15 am UTC Likes: 2
Yet another regular day of live-services on Linux.It's actually even a little worse than that.
I've seen some reports of developers (not necessarily game devs, but any coding) who are running some WSL ( Windows Subsystem for Linux ) for development - and somehow some of that running while a game was running triggered some anti cheat systems to flag them.
So even Windows people just running some Linux stuff for completely unrelated reasons get hit by this nonsense...
This will only stop if the share increases to something like 5-10%.
Or whatever number is needed for publishers to no longer outright ignore a chunk of their customers.
Portal: Revolution drops Native Linux support to focus on Proton
8 Aug 2025 at 5:43 am UTC
Even now, with a share quadruple of what it was it still wouldn't.
Devs either do a native port for intrinsic reasons or they don't - outside pressure from an absolute minority is a complete futility.
If you can run your game without issues, you can run your game without issues. If the performance is good, it is good.
Everything else is secondary at best.
We've had plenty low effort, zero support ports.
And we had plenty good intentions of devs, who then realized there is actually some work to supporting an additional platforms, and as a consequence stopped. I'd argue it objectively would have been better if those never even tried, because their failure story is guaranteed to carry more weight than any success story (negativity bias & media echo).
Devs already comfortable with Linux are very welcome to do a native port.
But those who never even touched Linux, have no real intention to, and only push the "export to Linux" button? That's a huge risk likely to come back to haunt Linux gaming as soon as a platform-specific bug arises.
People are people, the social climate is what we live in, it is what it is.
What more than "on par" do you need when it comes to video games?
What do you actually want to be ahead of?
Run them faster? Video games are mostly platform agnostic code, any kind of serious performance bottleneck will be cross-platform. At the bottom of it all is usually a C/C++ (or other low-level language) core that is standardized and will thus also behave the same no matter where. MSVC, gcc, Clang, etc all perform within 5-10% of each other, with differences only showing up in (surprise!) platform-specific code.
Features, like eg certain GPU techniques? May be thinkable, but that, too, is mostly hardware-bound.
But nobody would develop such a thing Linux-first, with a 2-3% share.
The gist of everything is that for anything serious to happen, the share has to rise.
That "No Linux support, no buy" crap didn't lead anywhere. Neither did the friendlier variant, the "Linux port pls" begging.
As Valve and years of dedicated work on compatibility layers has shown, you rise the share not by pestering devs with minority demands, but by ease of adaptation and support. And good hardware ideas.
You'll just have to live with most people in the Linux community having realized by now that blind idealism leads nowhere and consequently calling others out when they show just that.
Somebody telling you to "just use Proton" is not an attack.
8 Aug 2025 at 5:43 am UTC
We used to point out games not working well natively on Linux for what they are: bad ports.We still do.
We used to ask for ports for each and every game we wanted to buy.... which basically never worked for obvious reasons.
Even now, with a share quadruple of what it was it still wouldn't.
Devs either do a native port for intrinsic reasons or they don't - outside pressure from an absolute minority is a complete futility.
Nowadays not only "I can run it." seems to be enough for most people.I am going to assume the first "not only" is too much, otherwise I don't get that sentence.
If you can run your game without issues, you can run your game without issues. If the performance is good, it is good.
Everything else is secondary at best.
They even started to actively ask developers to not port games.If a dev already shows clear signs of not being up to the task of doing and supporting a proper native port, that's an extremely good suggestion.
We've had plenty low effort, zero support ports.
And we had plenty good intentions of devs, who then realized there is actually some work to supporting an additional platforms, and as a consequence stopped. I'd argue it objectively would have been better if those never even tried, because their failure story is guaranteed to carry more weight than any success story (negativity bias & media echo).
Devs already comfortable with Linux are very welcome to do a native port.
But those who never even touched Linux, have no real intention to, and only push the "export to Linux" button? That's a huge risk likely to come back to haunt Linux gaming as soon as a platform-specific bug arises.
They even started to attack fellow Linux games asking for ports.Yeah, I doubt that - at least no more attacks than anywhere else on social media for any given topic or opinion.
People are people, the social climate is what we live in, it is what it is.
Using Proton will always be being second class citizen.A clear improvement over what Linux used to be: no citizen at all, and third class or worse often enough even if there was a port.
Proton will always have to chase whatever Windows comes up with.Nice platitudes. But:
Proton can at most be on par, but never ahead.
What more than "on par" do you need when it comes to video games?
What do you actually want to be ahead of?
Run them faster? Video games are mostly platform agnostic code, any kind of serious performance bottleneck will be cross-platform. At the bottom of it all is usually a C/C++ (or other low-level language) core that is standardized and will thus also behave the same no matter where. MSVC, gcc, Clang, etc all perform within 5-10% of each other, with differences only showing up in (surprise!) platform-specific code.
Features, like eg certain GPU techniques? May be thinkable, but that, too, is mostly hardware-bound.
But nobody would develop such a thing Linux-first, with a 2-3% share.
The gist of everything is that for anything serious to happen, the share has to rise.
That "No Linux support, no buy" crap didn't lead anywhere. Neither did the friendlier variant, the "Linux port pls" begging.
As Valve and years of dedicated work on compatibility layers has shown, you rise the share not by pestering devs with minority demands, but by ease of adaptation and support. And good hardware ideas.
But how about letting others have it their way?Nobody is stopping you.
You'll just have to live with most people in the Linux community having realized by now that blind idealism leads nowhere and consequently calling others out when they show just that.
Somebody telling you to "just use Proton" is not an attack.
Portal: Revolution drops Native Linux support to focus on Proton
7 Aug 2025 at 8:02 am UTC
Click on the profile -> block button.
7 Aug 2025 at 8:02 am UTC
Yes, YES!!! Keeping our (gaming) future tied so closely to Microsoft it's good great!Just a reminder to people that this forum has an ignore feature, in case you want to get rid of sideline ragers who never contribute anything of value to discussions they inject themselves into, are really just annoying everyone and should probably go outside to take some deep, relaxing breaths.
Click on the profile -> block button.
Portal: Revolution drops Native Linux support to focus on Proton
7 Aug 2025 at 7:54 am UTC
Last Epoch, TW Warhammer (the Feral versions just performs straight up worse, is months behind thus destroying mod support, etc. ), tons of Adventure Maker games (or Adventure Studio? You know, the one everyone and their mum use to create point & click games) have severe issues on Linux especially with windowing and input, Ark, Rust; and the list goes on and on.
That's not anecdotal but confirmed by all the error reports you see for issues and the suggested solution 9/10 times being "switch to Proton".
It is also confirmed by devs shutting down their Linux version because they don't want to deal with the Linux-specific issues (meaning they did have enough of those to be bothersome).
"Works for me" is always anecdotal and no argument when obviously lots of people are having issues.
Funny enough, one thread I've seen throughout all of this is that often the issue isn't actually in the stuff related to graphics (which is arguably the main focus of the work being done on Proton, dxvk, etc), but in the native libraries used for windowing & window refreshing, input, etc.
Surprisingly often, it comes down to usage of ancient SDL1 (which, please devs, just don't. Ever.).
So switching to Proton will solve the issues not because of some graphical bug, but because the native libraries used for the native Linux version are, frankly, crap - or outdated.
There are undeniably lots of cases where it does not work well for people - and then Proton becomes an option.
The other way around just doesn't happen because if Proton is the default already, there IS no native version to switch to.
When you look at ProtonDB and the games that are reported to not work there, they are overwhelmingly of the multiplayer variant. That's probably 70-80% of the less than 10% of games that are reported as worse than Silver - and we all know the issues there are not Linux, but devs opting for the blunt hammer to their cheating issues.
In other words, the chance that your (non-MP) game will work fine on Proton is way over 90%.
The chance that the native version will work just fine? Hard to say without official data (which I doubt anyone has), but given the amount of reports and sentiments you generally see, I doubt it is better than the Proton stats.
Of course I wouldn't recommend going for Proton straight away if there is a native Linux version - because most likely that will work just fine and it will also perform better in that case.
But the approach to just switch to Proton always to get a higher chance at having no issues at all seems at least understandable to me.
7 Aug 2025 at 7:54 am UTC
So is that a statistic or an anecdote? Because my anecdote is, nearly all the games I play are native, and I never have any problems. When I have problems it's nearly always with a Proton game not working, even though I play far fewer Proton games. Although lately my main annoyance is for some reason my Dosbox Steam games are just not starting at all. I haven't played MOO2 in ages now because of that.You can go to any gaming-based forum with some Linux users and you will always see many people say that they've had issues with native games that were solved by switching to the Proton version.
So I'd be wary of this kind of generalization. We both have anecdotes pointing in different directions, but I doubt either of us have data.
Last Epoch, TW Warhammer (the Feral versions just performs straight up worse, is months behind thus destroying mod support, etc. ), tons of Adventure Maker games (or Adventure Studio? You know, the one everyone and their mum use to create point & click games) have severe issues on Linux especially with windowing and input, Ark, Rust; and the list goes on and on.
That's not anecdotal but confirmed by all the error reports you see for issues and the suggested solution 9/10 times being "switch to Proton".
It is also confirmed by devs shutting down their Linux version because they don't want to deal with the Linux-specific issues (meaning they did have enough of those to be bothersome).
"Works for me" is always anecdotal and no argument when obviously lots of people are having issues.
Funny enough, one thread I've seen throughout all of this is that often the issue isn't actually in the stuff related to graphics (which is arguably the main focus of the work being done on Proton, dxvk, etc), but in the native libraries used for windowing & window refreshing, input, etc.
Surprisingly often, it comes down to usage of ancient SDL1 (which, please devs, just don't. Ever.).
So switching to Proton will solve the issues not because of some graphical bug, but because the native libraries used for the native Linux version are, frankly, crap - or outdated.
There are undeniably lots of cases where it does not work well for people - and then Proton becomes an option.
The other way around just doesn't happen because if Proton is the default already, there IS no native version to switch to.
When you look at ProtonDB and the games that are reported to not work there, they are overwhelmingly of the multiplayer variant. That's probably 70-80% of the less than 10% of games that are reported as worse than Silver - and we all know the issues there are not Linux, but devs opting for the blunt hammer to their cheating issues.
In other words, the chance that your (non-MP) game will work fine on Proton is way over 90%.
The chance that the native version will work just fine? Hard to say without official data (which I doubt anyone has), but given the amount of reports and sentiments you generally see, I doubt it is better than the Proton stats.
Of course I wouldn't recommend going for Proton straight away if there is a native Linux version - because most likely that will work just fine and it will also perform better in that case.
But the approach to just switch to Proton always to get a higher chance at having no issues at all seems at least understandable to me.
Portal: Revolution drops Native Linux support to focus on Proton
6 Aug 2025 at 4:58 am UTC Likes: 2
But I see one problem: What do devs actually do in case there is a bug in their game specifically with Proton? Do debuggers, etc. work normally through the compatibility layer?
6 Aug 2025 at 4:58 am UTC Likes: 2
As long as it's fully playable via Proton, I don't have any problems with that.In theory, I agree with that.
I'm aware that maintaining native Linux games can be nasty for game devs.
But I see one problem: What do devs actually do in case there is a bug in their game specifically with Proton? Do debuggers, etc. work normally through the compatibility layer?
Developer of PlayStation 1 emulator DuckStation threatens "removing Linux support entirely" but not yet
1 Aug 2025 at 4:19 pm UTC Likes: 1
tl;dr: Works fine for me. Not with all the bells and whistles of Duckstation, but works great on my Steam Deck retro station.
1 Aug 2025 at 4:19 pm UTC Likes: 1
I am curious, what's the TLDR?About Mednafen?
tl;dr: Works fine for me. Not with all the bells and whistles of Duckstation, but works great on my Steam Deck retro station.
- Epic Games just laid off over 1,000 people
- Horizon Chase Turbo is getting delisted after the Epic Games layoffs
- Proton Experimental brings fixes for Crimson Desert, Steam Overlay with EA games, Death Stranding 2
- Behaviour Interactive have acquired 7 Days to Die developers The Fun Pimps
- Forza Horizon 6 confirmed to be playable on Steam Deck / SteamOS
- > See more over 30 days here
- New Desktop Screenshot Thread
- tmtvl - Thrustmaster TMX drivers for Linux
- Kxzrt - Proton/Wine Games Locking Up
- Caldathras - I think I found my Discord alternative
- ridge - steam overlay performance monitor - issues
- Jarmer - 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