Bulletdust

joined 2 years ago
[–] Bulletdust@lemmy.ml 1 points 1 month ago

Thanks for the response, I actually figured it out.

If I run GE-Proton9-27, Frame Gen works fine. If I use anything newer than GE-Proton9-27, I get the DLSS option, but only AMD FSR3 Frame Generation - It seems like a regression with recent Proton builds, as it also happens under Steam Proton 10.

I might try running a newer version of Proton when I get time and see if the launch option you've quoted resolves the issue, right now I'm just glad to have Frame Gen working again.

 

Running KDE Neon 6.3.5, Nvidia 570.144 proprietary drivers, an RTX 4070S.

I'm not too sure just when this started, but I no longer have the option to enable Nvidia Frame Gen, I only have the option for AMD FSR3 Frame Generation - Which honestly isn't as good.

I think the issue may have presented itself when SteamDeck=1 %command% became a hard pre requisite to run the game?

Is anyone else seeing the same behavior, or is it just me?

Steam launch options below:

gamemoderun mangohud LD_PRELOAD="" SteamDeck=1 %command% -PSOCompileMode=1

[–] Bulletdust@lemmy.ml 3 points 2 months ago* (last edited 2 months ago)

My biggest issue gaming under Wayland is the fact that certain games can't capture the mouse when run full screen with multiple monitors. I've got a number of games that exhibit the issue, but the easiest way to experience it is to try and run CS2 as wayland native (so not under xwayland - As the performance overheads running xwayland are notable running CS2) - Within 10 mins you'll be looking at the ground with the mouse pointer on your secondary monitor.

Furthermore, running gamescope doesn't fix the problem - And yes, I'm running the correct commands under gamescope.

I mean - This is basic functionality that should be an integral part of any modern OS. Under X11 running the same dual matched monitors everything works perfectly with great FPS.

[–] Bulletdust@lemmy.ml 0 points 4 months ago* (last edited 4 months ago)

I have no beef in this argument, and I'm certainly not biased in relation to AMD/Nvidia. However, my 980Ti, my 2070S and now my 4070S have all run really well under Linux. I run KDE Neon and a quick 'sudo apt install nvidia-driver-570' installs the latest beta's in under 5 mins, if I want to roll back the driver a quick 'sudo apt install nvidia-driver-565' has me back on the latest feature branch. Yeah, Wayland adoption under Nvidia was slow, and Nvidia's earlier choices weren't what anyone could call 'ideal' - But momentum is building, and as a result I've been using Wayland for about eight months now without issue. Before that, X11 was largely faultless running Nvidia hardware/drivers.

People say Nvidia struggle in relation to VKD3D performance. I'm not too sure what they're doing, but VKD3D runs fine here.

It's the one advantage we have over Mac users: We can run AMD, Intel and Nvidia. We also have ongoing OGL support, native Vulkan support, better game support under Steam, a larger user base under Steam, and the amazing Proton implementation.

Whether it be AMD or Nvidia, I personally think it's Linux for the win. EDIT: I in no way see value for money in the new 5080/5090 cards and I eagerly await what AMD has to offer (although I won't be switching from my 4070S for quite some time yet).

 

Currently running Battle.Net version 2.21.2.14215 with Battle.Net update agent version 2.30.7.8279, and Battle.Net keeps claiming an update is available, however when I select 'Update now' Battle.Net just closes. If I stop Battle.Net from within Lutris and reopen it, after a while Battle.Net notifies me that there's still an update available. I even tried selecting 'Install another version' under Lutris, which downloaded and installed a new Battle.Net instance, and I still have Battle.Net telling me there's an update available.

Anyone else encounter this? Does anyone know of a fix?