Can it pre-load shader cache like steam games does? Because that’s a big plus to running games on the higher half of the graphics demand side. Otherwise you’ll still need games to be steam in order to get the best performance.
Yeah. Good point. The problem I see with that is that SOMEONE has to store the shader caches that you download. With some games, it’s megabytes and some games it’s gigabytes. Also, the shaders are different for different hardware configurations. Who is going to not only store, but share all of this data when only a small portion of people donate to FOSS? Steam, gets a portion of the sale, and moving people to Linux is a far sight goal that they are monetarily incentivized to help towards.
True, but complex and probably a tad unrealistic. My old days of using torrents taught me that people don’t typically seed.
Ignoring that, if you automatically download torrents and start seeding them many people wouldn’t understand them and will have their internet overwhelmed and blame Linux, or Google it and come to the conclusion to “turn off the seeding feature”.
Also, Shader Caches get changed/updated CONSTANTLY. When I first got my Steam Deck, I was getting Shader Caches updates every time I turned it on for nearly every game. That has slowed down a lot but torrents specifically wouldn’t be the best solution for something that changes frequently. You can re-check so that you can just only download new caches with the latest torrent. But the re-check can be computationally expensive as well.
Idk the answer and I love the idea of P2P. But, we’d have to be careful to implement it well.
Magicland, I suppose. I guess it would need to spoof that it’s a steam os installed game in order to download the cache from valves server and then move the cache over to the appropriate folder for the game. I guess it would be a lot of work for each game, since the cache folder isn’t going to be named the same and in the same spot.
Even then, the shaders for steam deck wouldn’t work on other devices with different GPU architecture. I think it might require the same CPU architure as well. But, I’m not confident on the second part.
I wasn’t talking about other devices. Just the steam deck. If it’s a game bought through steam you get the pre-cache files. If it’s a game you’re playing on the SD, but was purchased/obtained outside of steam you can still play it but you won’t have the pre-cache files to use.
Yes and no. I could hop on to a 50 year old Unix machine and operate it pretty much the way I use my contemporary Linux computer, thanks to the standard Unix tools being both great and ancient.
There’s a lot of projects to help get Windows games working better on Linux, and this effort is basically all those projects coming together to work on making the ‘ultimate’ project that will make it easier than ever to game on Linux! :D
Well the interesting part of this is that they will collaborate on the engine but the frontend will still be independent.
I think this is a sound strategy (if I understood it well) as the key differentiators remain but the hard parts (running the damn things) become collaborative.
This also IMO helps a lot user experience, as dealing with broken scripts, mysterious wine settings and keeping up with version changes makes playing a game a big ordeal compared with other platforms (In some cases like old games, it can be worse).
I’m actually kind of surprised that they’re all working together at all. Normally they all wanna have it done their own way and it ends up just being another random project, that everybody loves until the next person creates another project because they want it done another way.
Indeed. However it’s necessary to use that command on both the main PID and all its child processes, otherwise you will run into issues like the game video stopping but the game logic still running in the background.
This is just a tool to automate finding the pid (via hyprctl or other ways) and correctly suspending it.
linux_gaming
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.