• priapus@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    1 day ago

    Steam is supposed to handle installing the Ubisoft launcher during the first-time setup, it sounds like for whatever reason it failed to do that. It’s very likely that verifying the game files would’ve fixed the issue easily, as it re-runs the first time setup. If that didn’t work, deleting the compatibility files would probably have been the next step. I’d be very surprised if one of these didn’t fix it.

    The rest of the troubleshooting steps you took until the GPU stuff were unnecessary, as they were basically Windows troubleshooting steps, not Linux ones. It’s completely expected to have to relearn how to troubleshoot stuff on a different OS and I’d really recommend asking in a Linux gaming community when you run into issues like that, until you’ve gotten the troubleshooting steps down.

    Install Ubi launcher using method ‘add installer as game, set compatibility layer, install and change executable for application executable’ … Install Lutris and install Ubi launcher through that

    Wine/Proton games are run in their own individual “prefixes”, which are essentially individual Windows instances. Both of these steps just installed Ubisoft launcher in a different instance. This would be a fine fix on Windows, but this is a different OS. The correct fix isn’t necessarily harder either, just different.

    Install Protontricks through Flatpack instead of system package, as the Flatpack version is slightly newer. Accept that this will result in a much larger installation due to not using system-provided libraries.

    “much larger” is relative, software is pretty small in general, especially compared to any modern games. It’s really not much space, and the flatpak runtimes will be reused for other flatpaks you install.

    As much as I want to like it, this experience makes me feel that Linux is not fully ready for the masses yet.

    I don’t even entirely disagree, but also don’t think the issues you faced completely demonstrate that. The Ubisoft installation issue was most likely a Steam client bug. First-time installations failing is 100% something that has happened on Windows, that’s why verifying game files is often the first recommended step when troubleshooting a game. Most distros that get recommended now have features to easily install Nvidia drivers. My personal recommendation for gaming, Bazzite, has an Nvidia ISO, which would’ve had them set up from the beginning.

    Do you mind sharing what distro you were using? It sounds like whatever it is has bad instructions for setting up Nvidia drivers, I’d like to avoid recommending it.

    Edit: Just read this back and wanted to add that I wasn’t trying to be rude or condescending at any point, or blaming you for the issues. I don’t think gaming on Linux is difficult, but I think people do need to do a better job preparing new users when they recommend it. It isn’t, and never will or even should be, the exact same as Windows. You have to learn the differences to be able to troubleshoot effectively, which just takes some time. Nobody knows how to troubleshoot correctly the first time they use Windows either.

    • Aganim@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      1 day ago

      I’m a bit strapped for time, so I won’t be able to touch on everything you said. But here goes:

      It’s very likely that verifying the game files would’ve fixed the issue easily, as it re-runs the first time setup. If that didn’t work, deleting the compatibility files would probably have been the next step. I’d be very surprised if one of these didn’t fix it.

      Of course I had to condense the experience a bit for readability and I don’t remember every step, but validating the game files, doing a reinstall and trying different Proton versions were parts of my troubleshooting steps. They absolutely didn’t work. I didn’t try removing the compatibility files afaik, but switching versions should basically have had the same result as that did trigger an first-time setup each time. The Ubisoft installer wasn’t part of that install for as far as I could see, or failed for each proton version without any visible signs.

      The rest of the troubleshooting steps you took until the GPU stuff were unnecessary, as they were basically Windows troubleshooting steps, not Linux ones. It’s completely expected to have to relearn how to troubleshoot stuff on a different OS and I’d really recommend asking in a Linux gaming community when you run into issues like that, until you’ve gotten the troubleshooting steps down.

      Linux is far from new to me, but gaming is a whole different beast compared to what I usually do with it. The steps I took were the recommendations from Linux gaming communities I came across. Even though I already suspected that the whole ‘install the Ubisoft installer through Steam’ wouldn’t work, if it is suggested, I’m not one to ignore that.

      The problem here is mostly that the information offered on various locations differs and it is a question of trial and error to find out what works and what not, especially if you’re still figuring out the gaming ecosystem.

      “much larger” is relative, software is pretty small in general, especially compared to any modern games. It’s really not much space, and the flatpak runtimes will be reused for other flatpaks you install.

      From the top of my head it was 3 GB vs 160 MB. Which is quite the difference, especially if you’re working with a relatively small SSD. Flatpack is a mixed blessing in that regard, it’s not meant as criticism against Flatpack, it’s just a trade-off of having sandboxed applications.

      Do you mind sharing what distro you were using? It sounds like whatever it is has bad instructions for setting up Nvidia drivers, I’d like to avoid recommending it.

      It was Linux Mint, on an Nvidia Prime-based laptop. Drivers were included by default, no installation required, but couldn’t load due to not being signed. Hence the ‘turned off Secure Boot’. I could have MOK’ed around and signed them, but at that point I simply couldn’t be bothered anymore and just went for the simplest solution. Not sure it were official drivers or Nouveau.

      Just read this back and wanted to add that I wasn’t trying to be rude or condescending at any point, or blaming you for the issues.

      No worries, even though I don’t fully agree with you on everything, I appreciate your response and the fact you are trying to help out. I already saw somebody else mentioning Bazzite, so my next attempt will be to try that distribution.

      I also noticed some ‘Ubisoft is just shit’ remarks, which might be true, but telling aspiring Linux gamers “well, you shouldn’t play that part of your gaming library anyway” is simply off-putting and unhelpful. So thanks again for being constructive, that’s what this community needs.

      • djsoren19@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        24 hours ago

        Linux Mint

        As someone who just ditched them, apparently here was where you went wrong. Trying to get Nvidia drivers working on Mint for gaming is bad enough that some documentation for programs I’ve wanted to run has straight up said “Don’t even try this on Mint.”

        Real shame because I liked a lot about Mint, but I would like to be able to run games like Warframe and Last Epoch more. I wish they were a lot more up front about the issues the distro seems to have with Nvidia.

        • cisor@feddit.uk
          link
          fedilink
          English
          arrow-up
          1
          ·
          13 hours ago

          Not denying you’ve had trouble, but my experience of Linux Mint gaming was

          • Install Mint
          • Install Steam.deb
          • Install Nvidia driver
          • Install games
          • Play games

          Only game that didn’t work first time was Star Wars: The Souls-like One With the Ginger Jedi. Tried a few months/updates later and it worked