• 0 Posts
  • 227 Comments
Joined 11 months ago
cake
Cake day: August 4th, 2023

help-circle



  • I can understand that Valve doesn’t want to give false impressions that a game runs perfectly when there are imperfections as mentioned

    Idk, I disagree with this. It means that games are being labeled as “not verified” because of things that don’t really hamper what people would care about - the keyboard popping up for naming your character or seeing “A” in a green circle isn’t going to make people be like “oh no, this doesn’t work well on my steamdeck, I’m not playing it”. Does it look unprofessional? Sure. But that’s not what people care about when looking at the ratings for compatibility. They just want to know if it’s going to run well.

    These systems are all about trust and evaluating the right metrics. Having the right button icons matters to Valve but not the player. Once players play games that aren’t verified and they run fine, and they play games that are verified but still have performance hitches in some places, etc, the rating system loses its credibility and then it’s meaningless.

    On top of this, developers are already shunning the verification and just not bothering. Some of the things they ask for don’t directly affect the playability of their game. It’s an extra hoop for the developer to jump through, and if people don’t trust the badge, there’s no point in chasing it. Valve is literally undermining their own system from both sides by doing this.

    There’s already people in this thread touting protonDB being a better evaluation. It’s exactly this that will happen and will continue to happen and continue undermining their rating system until Valve aligns their verification system with what users actually care about.


  • I’d actually bet it’s something different…

    It’s less that you game on a steam deck because it’s portable, and more that because it’s portable you can game. There are people here and there that are like “yeah, I have a steam deck so I use that instead” but the sentiment I see more often is “I wouldn’t be able to game at all if it wasn’t portable - I can’t sit down for that long, I only have time on the train, I need to be near my kids” etc.

    And this changes the dynamic. It’s less that these people have “desktop gaming” and “portable gaming” and are choosing to play the AAA games while portable. They only have portable gaming. And they choose to play the same good games everyone else is playing. The only gaming they do is on their deck. And they’re not going to be like “oh, why play a good game like BG3 if I can play a shitty portable game like xyz”.

    These are just people’s primary gaming devices now. And if they can, they will choose to play the same good games everyone else is choosing to play. It doesn’t matter if it only runs OK, playing a good game with OK graphics is still better than playing a shitty game.









  • I can’t agree with this more. People like to sell Linux as a magic bullet, but it does not and will not everything everyone needs without maintenance and people really like to hand wave or downplay that need.

    Sure, you could find a solution for what they’re using now. What happens when they need something else and they’re so tech illiterate that they don’t even know what you did to their machine? They wouldn’t even know how to install new software, and if they did, they wouldn’t know they need to click the Linux version, etc. It’s not always about feasibility and available options, it’s often about the fact that people just won’t fucking know what to do. Even if you assume there are enough options available, they won’t know how to do so.

    And every step Microsoft takes to shoot themselves in the foot, and every step Linux takes to make this easier, everyone comes screaming about how much this could change things.

    But until Linux has a HUGE market share - like in the 30-70 percent range - developers are not going to take it seriously and alleviate this process. Even with how well MacOS does, this is not even a solved problem entirely there - there are still hang ups and still software that doesn’t get released for mac. Linux would have to pass where Apple is today for this to become remotely accessible to an every day person.

    And even THEN there’s the question of different Linux distros.


  • I really do not understand how server anti cheat is not way easier.

    In a clean slate, it is. It’s also way more effective (except for things like wall hacks, aim bots, recoil suppressors, etc, but most of those things are only really important and popular in competitive FPS). It’s also much simpler to understand and to leave no “holes” behind. It also lives in the developers domain so it can’t be “compromised” or circumvented.

    The thing is that client side “anti cheat” can be commoditized. Every game with server authority/anti cheat needs specific server software to run their game logic. Client anti cheat is basically “look at everything else running on the system and see if any of it seems suspicious”. As such, there’s not really anything “game specific” to these - they basically are just a watch dog looking for bad actors - so as such, one company can come along, make one, and sell it to other devs.

    This being “off the shelf” and not something the dev team has to think about besides a price tag means that management is just going to buy a third party solution and check off the “anti cheat” box on their task list.

    I feel like devs are caught up on realtime anti cheat and not willing to do anything asynchronous.

    First, this is a management problem and not the devs. Any dev worth their salt knows this isn’t really a good solution.

    But I’d say the more relevant and prominent thing here is that game companies just don’t want to have to run servers anymore. It’s a cost, requires dev time, and requires maintenance, and they don’t want to do that. If these games had servers running the game world like games used to, they’d inherently have their own “anti cheat” built in for free that wouldn’t necessarily catch everything but would do a better job than some of these. And it could be enhanced to cover more bases.

    But studios don’t want to do this anymore. It’s easier to make the game p2p and slap an off the shelf anti cheat and call it a day.

    Some games still require matchmaking servers etc, but the overhead there is way lower.

    Or they really like paying licensing fees for client-side anticheat.

    Not that I agree with the decision, but it is definitely cheaper and faster than the alternative. But picking something like nprotect totally fucking baffles me. There are better options.

    I just don’t understand how any competent software engineer or systems admin or architect trusts the client so fervently.

    In some ways, same. Every project I’ve been on that has gotten anywhere near client side trust I’ve fought adamantly about avoiding it. I’ve won most arguments on it, but there are some places where they just utterly refuse.

    But then there are things like New World… I don’t know how the fuck that shit released like it did. The number of things trusted to the client were absolutely baffling. I expected Amazon’s first foray into gaming to be a fucking joke, but I was totally appalled at how bad it turned out. They even touted hiring ex blizzard talent to get my hopes up first.





  • And coincidentally YouTube, Spotify, and Amazon Music, all of Apple Musics competition, just all happened to not implement this? All of Apples competition just decided to not add a pretty critical function to the people of that ecosystem? When they all do it in Google’s?

    Yeah, I don’t buy that. At all. Sure the API might be there, but you know who gatekeeps those APIs? Apple. This smells a lot more like Apples fued with Google over turn by turn directions bullshit. Especially when we can see how blatantly hostile to Spotify Apple is willing to be.

    It seems a lot more likely that Apple is holding that API over their heads and refusing to allow access to it, than it does that all their Apple Music competition just happens to have all conveniently forgotten to implement a pretty core feature in Apple’s ecosystem, while remembering to do it in Googles.