No that perspective is what makes me understand that when corporations talk about obsceleting things for security reasons, it’s almost always not actually because of security, because it would be a little less profitable to continue support.
And Valve didnt have to build a business around always checking in DRM if they didn’t want to support old clients, and they have more than enough resources to continue support.
Literally any game sold that didn’t include always checking in DRM through a particular desktop client. i.e. virtually every single PC game not sold through steam.
Literally every software company built their business model this way. Go open a support case with any software vendor complaining that their product won’t run on Windows 98 and see how many help you out beyond “Buy a computer from this millennium”
No, they didn’t. I can install the software I bought back in the day on the computers I bought it for, using the license key provided. GoG also famously uses a model where GoG does not care what OS you’re using.
You are failing to understand just how much has changed since Windows 98. It’s a completely different environment that requires specialized knowledge to develop for. They can’t just dust off some old source code and re-release the client. The entire back-end has changed. It would be a massive undertaking that would appease about 12 people total.
Lol, I’m a software developer that started by writing legacy windows software, I know exactly how much (little) has changed.
Sure, but I would argue that there are a lot of better things that Valve could be doing with those resources than supporting Windows 98
I don’t care. They have the resources to support it.
Either strip the DRM out and pay whatever you have to to the publishers to do that, or keep supporting the systems you sold your software for.
The idea that Valve is blameless for shitty behaviour because other tech companies also do that shitty behaviour is nonsense. They have been the dominant platform forever, and have had an insane amount of resources available to them.
In my opinion, that’s not on Steam to support their client on a long past EOL operating system.
It is on them since they “sold” you a game. They didn’t have to build a business model that popularized always checking in DRM, that meant that they were deceiving you when they sold you a game, but it was more profitable for them to do so.
Valve expects that the overwhelming majority of its users will keep up with semi-modern hardware (In this case, a machine capable of running windows 10/SteamOS) which I don’t feel is is an unreasonable ask.
Valve is forcing them to upgrade their software and hardware to keep playing games they already purchased, on the hardware they purchased it on.
However, expecting Valve to retain support for an OS that hit end of life 20 years ago is unreasonable.
It is very reasonable. No one forced Valve to build their business model this way, and they are one of the most profitable companies per employee, ever. It would not be onerous for them to continue supporting a couple of old versions of Windows, they would just have to hire a few more people to do it. Gabe would still be a billionaire.
The author of this article reflexively and illogically defends Steam (like usual):
But at least some of what Kaldaien complains about isn’t necessarily on Steam’s shoulders. It’s well within devs’ powers to provide players with access to older game versions on Steam (KOTOR 2, which I recently replayed, lets you access its pre-Aspyr version via a beta branch, for instance), but many of them elect not to. That strikes me as an issue with individual devs rather than Steam as a whole, and as for Steam Input? Well, again, if there’s a problem there it’s with developers electing to use that API over OS-native ones that’s the issue.
He literally completely misses the modder’s point. Steam itself will not run on the original machine you purchased KOTOR 2 on. You can buy a gaming machine, purchase a game through steam and 6 years later, one random day you’re suddenly no longer able to play your game, simply because Valve has decided that the version of Steam that you bought the game through is no longer ok and now you need to upgrade your hardware and OS to play the same game you’ve been playing for years.
the pinning system with filters is handy for food, but feels clunky outside that one usecase.
The pinning system is an improvement over not having a pinning system that should exist in every game. Food, water, ranged weapons, explosives, healing items, shields, even melee weapons, it makes sense for all of them given that all of them can break.
Conversely, Grounded has the best inventory management system of any survival game ever.
To the point that I have a hard time playing others now because they all feel tedious in comparison. It’s hard to imagine someone playing Grounded and then building a survival game that didn’t use hot deposit.
To be fair, they didn’t gut the original creative team.
Max McGuire was CTO and a programmer on the original game, Ted Gill was President and a Producer on Below Zero.
Charlie Cleveland was current CEO, and the director and lead designer of the original game, so was the head of the origin creative team, and that does seem like a big loss, but no one else from the art, writing, or design teams seem to be leaving, so it’s not really a ‘gutting’ of the original creative team.
My guess (especially given how buggy Subnautica was), is that they were missing their delivery milestones so the publisher wanted to replace the organization heads and move at least Charlie Cleveland back down to a creative role, but they refused and left together.
If this hasn’t remotely been your experience, how do you know rainbow flicking fixes it?
It doesn’t fix it, it’s how you avoid letting get that close to you.
The game is widely known to have multiple bugs affecting gameplay, from lags and desync issues, to crashes and even teams changing colour mid-match. In this case, and this is the second time I’ve seen it, the ball glitched into the ground after randomly bouncing around the pitch following a shot against the post befote finally getting stuck. It couldn’t be interacted with at all.
Well if this is a bug, you should probably make that clearer, because again, have not encountered a single bug.