59
[Guide] Everything you need to know about gaming on Linux (popcar.bearblog.dev)
submitted 3 years ago* (last edited 3 years ago) by to c/linux_gaming@lemmy.world
25 comments fedilink hide all child comments
 

Hi everyone, I just finished writing a guide on everything you need to know in order to game on Linux. It covers Proton (Steam play), using Heroic Launcher (with Wine-GE), and all sorts of tidbits and tips I wish people had told me earlier. I hope this can be useful to someone out there!

Archive link: https://web.archive.org/web/20230816141640/https://popcar.bearblog.dev/everything-linux-gaming/

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 3 years ago (1 child)

Nice article. Thought about putting it on github /gitlab? It would be interesting to hear your thoughts on non flatpak for steam and flatpak for heroic.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 0 points 3 years ago (1 child)

    Thought about putting it on github /gitlab?

    I'm not opposed to it, but is there demand for it to be on GitHub?

    It would be interesting to hear your thoughts on non flatpak for steam and flatpak for heroic.

    Steam's Flatpak version has some issues, the way it's sandboxed causes things to not work as it should. I've seen people complain about controllers not being detected via Steam Input, confusion around permissions, minor bugs among other things. There's really no reason to use that instead of your package manager.

    On the other hand, Heroic actually recommends the Flatpak by default since it's stable, has no issues, isn't distro-dependent, etc. There's no reason not to use it instead of your package manager.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 years ago* (2 children)

    I'm not opposed to it, but is there demand for it to be on GitHub?

    There is! These sort of guides are best suited to be hosted at Github/lab because of their dynamic nature. Any recommendations and "best practice" today might easily become outdated tomorrow in this fast-moving Linux world! Plus you can have contributors too submitting corrections and updates (if you wish to merge 'em), so you're not left alone doing all the work.

    Here's an example of one such guide I've used in the past that's still being updated:

    https://github.com/AdelKS/LinuxGamingGuide

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 3 years ago (1 child)

    I think a dedicated wiki makes more sense for what is, essentially, documentation.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago (1 child)

    Yes, in theory. In practice, Github has become a hub for such living documents, especially in the Linux/OSS world, so it isn't strange for people to look there for guides and recommendations.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago

    As someone who recently worked on a Github wiki...it leaves much to be desired. The first being that I couldn't actually push with git! I needed collaborator access for that. I also find Github's markdown flavor to be limiting; you can do a lot more with a dedicated Wiki like MediaWiki. It was okay for viewing, though. And having the docs in an actual repository is much harder to navigate for users who aren't developers.

    So while it's something you see a lot, I think they would be easier to collaborate on and view on a dedicated wiki.

  • permalink
  • fedilink
  • source
  • parent