million

Does the community have any thoughts on Bazzite for a desktop gaming machine?

My primary use with be mouse and keyboard, but the deck interface looks nice for the 10% of the time I want to use a controller. I also hear that HDR and VRR work better under it then most of the DEs.

Anyone out there using Bazzite for a similar use case? I'd also be curious to here about other ways people are using it.

Background: My monitor has a local dim option that produces flicker when combined with VRR. So for games where I care about HDR I have been turning off VRR.

My question is, to avoid judder and have evenly paced frames, what is the recommendation?

I have a max refresh of 160 so if I can’t hit that consistently should a cap at something that divides evenly into 160? For instance, 80 or 40. Should I avoid other common frame caps, like 60 or 120?

This is one is very confusing, which probably speaks to the current UI in Heroic. I just want to say, run this game in gamescope, so I can use HDR.

I have the latest version of Heroic, installed via Flatpak as the devs recommend. If I go to configure the game in the UI it has an entire settings page dedicated to Gamescope but nothing that says "enable gamescope".

Anyone get this working?

Under Windows this is an option in the AMD control panel. Not sure how to enable it.

Specifically, this is for a non-native Proton game with FSR support built in. I am not using GE as I need the latest code in Proton experimental to run this game.

Hey Folks,

I had Diablo 4, the Battle.net version, running perfectly fine under Lutris Flatpak. Then randomly one day it just stopped working, I didn't download a new version of the wine runner I was using, I didn't make any configuration changes it just broke. Specifically it boots, the screen goes grey for a few seconds, and then it loads up super slowly, like 1 fps and makes the game interface and Plasma becomes unusable, so I have to drop to a TTY to kill the process. Nothing really interesting is show if I select "show logs" in Lutris.

I was thinking some Flatpak Lutris update broke it, so I tried to install the game using Bottles, also a Flatpak, but ended up with exact same problem. Now I am thinking this may be a Mesa problem since that is a dependency both of these Flatpaks share. I am using the same Wine GE version on both, but it's a version from February and it worked just fine a few weeks ago.

Any recommendations on what I could do or what I could look at to debug further?

I have 2 drives in my machine. Linux right now is installed on 1/4 of the first drive and I am going to start moving parts of my 2nd drive, which is just games on Windows, to a 1/2 combo of NTFS and BTRFS. Essentially giving Linux more space as it replaces Windows as my gaming daily driver. With the eventual plan to move that entire 2nd drive over to BTRFS, and allow Windows to have 3/4 of the 1st drive for games that only run under it.

Curious how folks have set this up. Currently I have Steam, Heroic and Lutris installing to ~/Games. So it may make sense to mount my new drive there, but I am not sure that in home folder mounts make sense. I also realize I could potentially use BTRFS to make it look like my space is all one mount point vs multiple, but given the complexity of that filesystem I am worried there is a downside I am not aware of.

Any suggestions? What has worked for you for your setup?

I am using the Steam Flatpak on OpenSuse Tumbleweed and when using the Steam interface, specifically when I get a chat message or try to respond to one, the Steam UI will hard freeze, as in a I can't type or move windows or interact with anything and then 30 seconds or so later everything goes back to normal. Plasma is still response when all of this is going on, it's just the Steam UI that freezes.

It's super odd and I have been running the Flatpak in the terminal to see if I can chat any relevant log messages but haven't seen any yet. It's been a little bit since I used the OpenSuse package and I think I remember seeing these freezes occasionally, but they seem much more common on the Flatpak version.

Anyone else get this behavior?

Not sure what happened but I've been running Steam games using MANGOHUD=1 gamemoderun %command% and it's been working fine with Mangohud. Suddenly, no Mangohud. Mangohud still works with Lutris.

I am using the Flatpak version so I looked at my history and there haven't been any updates to the Steam or Mangohud Flatpaks when the breakage occurred. Nothing relevant is logged out if I run Steam using flatpak run com.valvesoftware.Steam. Inside Steam there have been a few updates, including an update to the common redistributable and that may have been around the time this broke. The only other thing I see is that Gnome updated some Flatpak stuff recently as well.

System wise I am on OpenSuse Tumbleweed using KDE Plasma 6. Any tips for debugging further?

Relevant Flatpak packages

Name                              Application ID                                Version  Branch       Installation
Valve Corporation                 com.valvesoftware.Steam                       1.0.0.79 stable       system
Mesa                              org.freedesktop.Platform.GL.default           24.0.3   22.08        system
Mesa (Extra)                      org.freedesktop.Platform.GL.default           24.0.3   22.08-extra  system
Mesa                              org.freedesktop.Platform.GL.default           24.0.3   23.08        system
Mesa (Extra)                      org.freedesktop.Platform.GL.default           24.0.3   23.08-extra  system
Mesa                              org.freedesktop.Platform.GL32.default         24.0.3   23.08        system
Mesa (Extra)                      org.freedesktop.Platform.GL32.default         24.0.3   23.08-extra  system
MangoHud                          org.freedesktop.Platform.VulkanLayer.MangoHud 0.6.8    21.08        system
MangoHud                          org.freedesktop.Platform.VulkanLayer.MangoHud 0.7.1    23.08        system
gamescope                         …g.freedesktop.Platform.VulkanLayer.gamescope 3.14.2   23.08        system
Freedesktop SDK                   org.freedesktop.Sdk                           23.08.14 23.08        system
GNOME Application Platform versi… org.gnome.Platform                                     45           system
GNOME Application Platform versi… org.gnome.Platform                                     46           system
i386                              org.gnome.Platform.Compat.i386                         45           system
Breeze GTK theme                  org.gtk.Gtk3theme.Breeze                      6.0.3    3.22         system
Adwaita theme                     org.kde.KStyle.Adwaita                                 6.5          system
KDE Application Platform          org.kde.Platform                                       6.5          system
DXVK                              org.winehq.Wine.DLLs.dxvk                     2.3      stable-23.08 system

New Humble Bundle supporting child’s play and the Trevor project

As the title asks, how does one actually use HDR for games after upgrading to Plasma 6?

This was the feature I was most excited about, and I can hit the HDR button on my display configuration and it looks like the desktop is going into HDR mode, but so far I have had zero luck enabling the HDR feature in games. Every game I've tried had the HDR toggle disabled with no way to enable it.

I am running these games under Proton and I've tried both 8-GE and 9 Beta. Any tips?

Edit: probably important to note that I am using an AMD GPU under Wayland

I was going to going to ask this question because Steam Flatpak was listed as last being updated May 2023, but they just updated it yesterday. That's still about 9 month between updates.

In general if I am on rolling release like OpenSuse Tumbleweed is my Steam package and Mesa drivers going to be more up to date then what the Steam Flatpak provides or are they updating the Flatpak and dependencies more frequently then the Discover app is suggesting?