Debian has all the packages one needs for gaming sufficiently updated to run games just as well as the other distros. It also has a better track record of not breaking, compared to rolling distros like Arch. Please stop spreading misconceptions.
Debian has all the packages one needs for gaming sufficiently updated to run games just as well as the other distros. It also has a better track record of not breaking, compared to rolling distros like Arch. Please stop spreading misconceptions.
I wonder if you would get different answers if you split your question into two:
Only if they measure their success in terms of traffic on a Microsoft web site.
Successful projects predate GitHub.
I read it as needing a Microsoft account, and having to accept Microsft’s terms and conditions, in order to contribute to an unrelated (and probably open-source) project. That’s a valid complaint.
Microsoft’s approach to their OS seems to be, “constantly add more stuff that relatively few people want or need, and require everyone to buy new hardware to support it.” The resulting upgrade cycle is needlessly wasteful of people’s money and harmful to the environment.
Meanwhile, the Linux ecosystem is more like, “make new stuff available, but optional, and constantly optimize things to be more efficient.”
I was still gaming and developing software on a ten-year-old computer (with a somewhat newer GPU) until very recently. I’ll let you guess which OS I was using.
Debian gamer here. Glad y’all are having fun, too.
“Oxygen.”
Troubleshooting software is a deep rabbit hole. Troubleshooting modern games, made for a complex operating system like Windows and running on another operating system, is a very deep rabbit hole.
However, since you’re just launching games through Steam, you probably won’t have to go very deep. This would be a pretty good place to start:
https://github.com/ValveSoftware/Proton?tab=readme-ov-file#readme
https://github.com/ValveSoftware/Proton/wiki
Note especially the FAQ
Wine is not a hardware emulator.
However, its very purpose is to emulate the Windows runtime environment. Translating API calls is only part of that. Also, the project abandoned that silly backronym years ago.
So kindly leave people alone when they refer to it emulating, or as an emulator, or something that emulates. They’re not wrong.
I just put the installers onto a thumbdrive.
I hope you’re powering up that thumb drive every few weeks. Flash memory will lose charge if left unpowered for too long, corrupting your data.
I like the idea. I would wait until Matrix 2.0 is officially released and implemented in the major clients. It will make a big difference to the user experience.
At least I linked to the code,
I appreciate that. :)
Here’s a fun fact not noted in the article:
It’s #19 in the article.
#17 mentions strict and links to its documentation.
One of the appealing things about the Steam Deck is its repairability. Valve even made the analog sticks modular, published a teardown video, and partnered with iFixit to make replacement parts available, IIRC.
It would be hard to convince me that a device that doesn’t beat the Deck in this area is “today’s best”. It’s important.
I find that OBS Studio does well if I use the VAAPI plugin (which uses my GPU’s h.264 encoder) instead of the ffmpeg one. However, OBS Studio is more fiddly than I would like for basic tasks like recording game footage. GPU Screen Recorder looks much simpler; I’ll have to give it a try.
“It is obvious to everyone: Elbrus processors are not yet at the level required to compete equally with the PS5 and Xbox, which means the solution must be unconventional.”
That unconventional approach could involve either simplifying games to the degree that Elbrus CPUs can handle (the Russian audience still has access to world-class games and would likely not play those ‘simplified’ games)
Oh, let’s not be hasty. Nintendo has had great success with underpowered consoles, and Tetris (Тетрис) is a shining example of this sort of thing. :)
Most of the web standards driven by Chromium are not particularly beneficial to the web, but are beneficial to Google. This is not an accident. It is how Google has made itself gatekeeper of the web while maintaining the facade of an open and standards-compliant browser.
This is not a good thing. Community-focused projects investing time and money into supporting it is a bit like digging one’s own grave.