I don’t have a reference, but I’ve been seeing random individuals asking for help and finally saying they fixed their issue by switching away from flatpak, so… You, I guess? Your.problem might be a perfect example of one of the many problems that keep popping up, that seem to only happen on the flatpak version.
I think you’re wrong about one thing - it’s not about compute cost, but about complexity of accounting for latency. You could check if the player can see the enemy they’re claiming to have shot, but you really need to check if they feasibly could’ve seen the enemy on their computer at the time they sent the packet, and with them also having outdated information about where the enemy was.
The issue gets more complex the more complex the game logic is. Throw physics simulation into the mix and the server and clients can quickly diverge from small differences.
Ultimately, compensating for lag is convoluted, can still cause visible desync for clients (see people complaining about seeing their shots connect in CS2 without doing damage), and opens up potential issues with fake lag.
More casual games will often simply trust the client, since it’s better for somebody to, say, fly around on an object that’s not there for other players, than for a laggy player to be spazzing out and rubberbanding on their screen, unable to control their character.
I suppose the thing I’m worried about is more general Linux SteamVR support than the streaming itself… But duh, the headset can run games on Linux standalone, so they’ve gotta have SteamVR working well. The only question is, am I behind on the news, or have they been holding back the updates internally?
I do believe they called out that the steam machine is designed to work with the frame, right? I’d have expected to see Linux SteamVR updates leasing up to this, to get it fully fixed up and tested ahead of time, though I might also have missed something…
Developers already care about it. Not all of them, not all the way, but many are aiming for steam deck compatibility via proton. It’s not perfect, and some devs are vehemently holding out, but it’s progress!
I think they decided not to, with some (IMO fairly) snarky comment on how that was just a proposal and people were getting needlesely outraged.
I don’t think either has ntsync support enabled by default, but it’s supposed to have better accuracy or performance, thanks to putting the needed APIs directly in the kernel, right?
The issue is that the privacy policy changed on an old game people bought long ago, and now they’re not allowed to play the game without agreeing to the changes.
Ah, sorry, I confused you for the original commenter. The first sentence is a bit nonsensical, it is a bit rude and snarky, but I meant it as a joke, since I had the wrong impression the person having issues with flatpak steam is asking about issues with flatpak steam.