Oof, sorry to be the deliverer of bad news. In another thread someone suggested to reach out to the developers and ask them about the future of Linux. I couldnt really find any place to reach out though, so if you have already bought the game, you could check whether the credits might mention contact details. Having already bought the game is obviously a better foot to stand on as well, so that might help the argument.
I had a similar experience switching from my GTX 1070 to a 6700XT last year. Things had improved significantly over the years I used the 1070 but the experience has been overall much more seamless after switching
I was having similar problems on a fresh arch install with multiple apps taking upwards of 15 seconds to launch, and the “fix” ended up being to uninstall one or more of the “portal” packages (there are several with names like xdg-desktop-portal-gtk). gitlab.gnome.org/GNOME/…/74 and bbs.archlinux.org/viewtopic.php?id=285334 for more info.
Could be completely unrelated, but it might be worth a try.
What desktop environment or wm are you using? Are you using a login manager or launching your session from tty?
I’ve had similar issues in the past but in my case I had to configure things so that when I log in it sets environment variables correctly and have my sway config start up xdg-desktop-portal correctly.
I’ve also had situations where specifically xdg-desktop-portal-gtk was causing problems so id uninstall that while keeping the other xdg-desktop-portal-* packages, so it could be one of those causing it
There’s FSR2 which is similar to DLSS without frame gen They’re also developing FSR3 which will apparently give “up to a 2x increase” of frames by also using frame gen.
A pro of FSR is that it’s open source so it’s easier for developers to put it in their games themselves.
Some annoyances exist though, like trying to use hardware en(!)coding while retaining the mesa drivers for gaming. HW Enc. is only available with the proprietary amdgpu-pro drivers, which are no good for gaming. You can work around that by using distrobox to setup an arch container on any distro and then using the AUR to install the proprietary drivers and obs in that container. That way, the rest of the system still runs on mesa, but obs loads with hardware encoding support. You can then export obs using distrobox-export -app obs-studio to make it available on the rest of your system like any other app. On nvidia, you install the proprietary drivers anyway, so obs will let you encode on hardware right away.
Ahh thanks this looks promising. The only thing that I don’t get from that article is where they talk about the nvidia gui settings. I’m not seeing that. Is that the same as the nvidia xserver application?
So I found the issue in case anyone comes across this. I had to switch to x11 gnome instead of wayland on the login screen in fedora 38. After that Diablo runs like butter!
it was actually the nvidia drivers that was in the install, had to modify the boot so i can download and install the proprietary drivers. everything is running perfectly smooth now :) i was using a 16gb USB
Good to know you solved your issue. I remember in Nobara 36 I flashed it onto a 4gb stick and it was pretty full. Wasn’t sure if the subsequent releases increased in size or not. :p
Had the same problem after upgrading from 37 to 38. Its an nvidia problem
1 - Boot an older kernel OR Drop to a TTY (Ctrl + Alt + F3) OR Boot into runlevel 3 (on grub, press ‘e’ when the list of kernels show, look for the line with quite splash nvidia-drm.modeset=1 and add the number 3 there, then Ctrl + X to boot) 2 - Login on your terminal and dkms status. If you see something like /var/dkms/nvidia/525.116.03/source/dkms.conf does not exist, remove the entire directory of the failed version rm -rf /var/dkms/nvidia/525.116.03 3 - sudo dkms autoinstall 4 - reboot if no errors and profit, otherwise rinse and repeat step 2-3
PS: If dkms tells you nothing at all (after the upgrade): remove the drivers /etc/nobara/scripts/cosmo-nvidia-wizard/remove.sh
reinstall them /etc/nobara/scripts/cosmo-nvidia-wizard/install.sh
If your dkms status is ok, you probably have a mismatch in your initramfs and root. just sudo dracut -f --regenerate-all and reboot
it was an nvidia driver problem, i have resolved the issue by editing the boot in grub by pressing e and setting ‘nomodeset quiet’ and reinstalling the propriety drivers upon boot
I had a 5700xt prior to my current 3060 and I’m very tempted to switch back so I can get rid of nvidia’s drivers, getting Wayland functional has been a disaster for me.
I just switched them like a couple weeks ago to give macOS another go, so I’m just being lazy 😅
I’m so mad at myself for impulse buying the rtx 3080… can’t wait to switch to team red completely in a couple of years. Or do you think someone is willing to swap their AMD for my nVidia card? 😂
Not really. In my case i start it from within Steam Library and not from commandline, but i have tried the --force -q dotnet48 shortcut also, with no positive result. Yesterday, I could play the game for more than 3 hours, but today, starting it the same way, it crashes after loading 1% of the save game.
I’m starting it now in a parallel installed Windows, where the save game location is shared between both OS (-appdata “/path/to/folder” -skipintro). Maybe i find a better way and must not boot to Windows. Since i start this really seldom, it has to download a lot of Updates before i can continue.
in the term that will open type “$@” (with the ") and inspect the output .You can redirect it, but steam executes games in a container so not all other directories will be available to write to
linux_gaming
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.