cross-posted from: lemm.ee/post/39456265

For those of you like me who are fed up with Microsoft’s BS but invested too heavily in hardware that Linux distros have yet to support well, I finally figured out a way to get HDR games to run well on my Nvidia GPU. This will be a brief description of more or less what I did to get this working. I’m very much a Linux noob so I don’t fully understand the way everything here works but I’m happy to try to answer questions if you have any.

OS: Bazzite –Desktop Nvidia KDE edition (BDNK)
Bazzite was developed as a capable alternative to SteamOS on handhelds like the Steam Deck and ROG Ally, so the website is full of references to HDR, however from my attempts to get this working my understanding is that it’s easier to get that working in Gaming mode which is unsupported on Nvidia GPUs. Nevertheless, this version of Bazzite, while only for desktops, comes with KDE Plasma v6 installed by default meaning it technically supports HDR and you will likely see a difference if you install this version and flip the HDR switch from the display settings. I had tried installing Ubuntu on my desktop before and since it didn’t support HDR all the colors on my monitor were almost obnoxiously saturated; I see the same effect in BDNK when I disable HDR.

Drivers: I didn’t fiddle with my drivers. BDNK comes with up-to-date Nvidia drivers bundled and installs them when you install the OS.

Software: SteamTinkerLaunch (installed using ProtonUp-Qt)
SteamTinkerLaunch (STL) is a user interface for making it easy to configure your launch options for any given game in your Steam library. If you don’t know what a compatibility tool is, it’s functionally a layer of software between the game you want to play and the OS you’re using which can tell the game to do certain things that your OS is not configured to do. STL can be added to the list of compatibility tools you have to use in your installation of Steam, though it is not technically a compatibility tool itself. STL is used to configure other compatibility tools that Steam already has at its disposal, like Proton which is the primary compatibility tool SteamOS uses to make Windows games run on Linux.

Follow the instructions in the SteamTinkerLaunch GitHub ReadMe to install the tool and add it as a compatibility tool in your installation of Steam. Once you’ve done that, I recommend rebooting. I have yet to get STL working as the * default * compatibility tool, so for the time being I have been manually editing the properties of each game I have installed (Steam Game Library > right click on a game > click properties > go to the compatibility tab) to set the compatibility tool to STL. From here, whenever you launch the game in Steam, it should bring up STL’s menu before launching the game.

Within STL, the key settings to mark are as follows:
Gamescope: Use gamescope and mark HDR as enabled for gamescope. I also recommend setting gamescope to fullscreen with your desired resolution, and then also locking your cursor to the gamescope window so that you don’t end up with weird double mouse cursors that aren’t aligned on the screen.
Proton: since you told Steam to use STL instead of Proton as the compatibility tool, you need to tell STL to tell Steam to launch the game with Proton.

And that’s pretty much it. Or at least, that’s all that I did. From there, you should be able to configure HDR settings within each game’s menus.

TL;DR – install Bazzite Desktop Nvidia KDE, then install and configure SteamTinkerLaunch for your games.

What games will this work with?
No idea. So far I have tested it with Cyberpunk 2077, DOOM Eternal, and Elden Ring and HDR is looking to me as good as it does in my Windows installation.

Will the Gnome version of Bazzite work for HDR on an Nvidia GPU, or for that matter any other OS as long as I’m using gamescope to run the game with HDR enabled?
Good question! I don’t know, please give it a try if you’re curious and respond back with your results.

I have another question that you didn’t list here, what’s your answer?
Probably “I don’t know” since what I wrote here is more or less what I know, but by all means ask away and I’ll try to answer it!

This week's news:
- @mmasnick joins Bluesky's Board of Directors
- @bonfire shows some more information on Mosaic, another project of Bonfire, and puts out bounties for developers to help get to a 1.0 release
- A platform for football fans with CollabFC
- 3d printing platform @manyfold has added early #activitypub support
[share author='Laurens Hof' profile='https://fediversereport.com/author/laurenshof/' avatar='' link='https://fediversereport.com/last-week-in-fediverse-ep-79/' posted='2024-08-11 17:09:02' guid='08552256-1ddb98c771664f15-878de609' message_id='https://fediversereport.com/last-week-in-fediverse-ep-79/']Last Week in Fediverse – ep 79

While we’re busy enjoying the summer (or the Olympics), here is this week’s fediverse news.

The News

Mike Masnick, author of the ‘Protocols, not Platforms‘ paper has joined Bluesky’s Board of Directors. There has been a seat available since Jack Dorsey suddenly left the board a few months ago. In his personal announcement post, Masnick says that ‘Bluesky is the service that is coming closest to making the vision I articulated in my paper a reality‘. Masnick also explains that one of the key aspects that excites him about Bluesky is how ‘they recognize how a future version of the company could, itself, be a threat to the vision the current team has. As a result, they are designing the system to be technically resistant to such a threat.’

With the current implementation of Bluesky, two parts of the architecture (the Relay and the AppView) are theoretically decentralised, but with no incentive structure for other people to also run an alternative part of the infrastructure, nobody actually has done so. Furthermore, the Identity part of Bluesky is still fully centralised and under control of Bluesky, with no clear path to change this. This places Bluesky significantly behind other major fediverse software, who are all already fully resistant to future self-harm. As Masnick values this principle, it is worth seeing how his position on the board will influence the direction of the development of the AT Protocol.

Two new fediverse projects that stand out to me for a similar reason; they both shift away from ‘microblogging about anything you want’ to a community that is clearly defined by interests or topics. CollabFC is a football-based social network, that creates a specific network for football clubs. When you join a hub for a club, such as Liverpool for example, you have the possibility for a ‘local’ feed dedicated to Liverpool, as well as a feed for all other football instances. Gush is a platform that is in development for talking about video games. Part review site similar to BookWyrm and NeoDB, it focuses on posting about specific games. What is different about it is that each game ‘a first-class object that you can reference and share across the fediverse’. Both of these platforms are early in their lifecycle, but point in a direction of more focused discussion on fediverse platforms.

Bonfire shared some more information about their upcoming platform Mosaic. Full details will be available in September, but it looks like a front-end UI for displaying posts as a website instead of the regular feeds. Something similar is Servus, a CMS for Nostr, or Npub.pro, which are both experiments for Nostr to display posts not as a feed but a website as well. Meanwhile, the main aspect that is holding up the release of the ‘main’ version of Bonfire is a slow performance, and the Bonfire team put out two bounties for developers to help them fix this issue.

Threads held an AMA about the fediverse with Flipboard’s Mike McCue and Blockparty’s Tracy Chou. It seems relevant that Threads wants to promote their fediverse connection by hosting an AMA on their main account, but there were little answers that stood out or provided new information, with most answers talking more about a conceptual understanding of what the fediverse could be, more than what the actual rest of the fediverse outside of Threads actually looks like.

Manyfold is an open source self hosted platform for sharing your 3d printer files. They have been working on adding ActivityPub support, and the latest update added experimental early stage support for ActivityPub.

Link aggregator platform Kbin is getting closer and closer to being completely dead, with the main flagship instance kbin.social now also being offline. The lead developer could not keep up with work on the platform due to personal reasons for a while now. The project has been superseded by the hard fork Mbin, which has been around for a while now, and got another update this week.

The Links

• Newsmast’s Michael Foster writes about ‘how can we persuade organisations and creators that it makes sense to federate using tools they already have in place’.
• Bandwagon, the upcoming fediverse music sharing platform, is expanding their beta test.
• Buffer recently added support for Bluesky, and the Buffer CEO wrote a blog post about the significance of Bluesky and decentralised social networks.
• Elena Rossini’s newsletter ‘The Future is Federated’ does an extensive deep dive into Friendica.
• WeDistribute takes a closer look at the successful ‘Mastodon for Harris’ campaign, which raised over half a million USD.
• Bluesky is summoning a community marketing manager.
• The new video series Fediverse Files by WordPress.com has a second episode in which they interview Evan Prodromou about ActivityPub.
• Font Awesome for the fediverse, with Decentralised Social Icons, by WeDistribute.
• A blog by Smoke Signal, an upcoming event platform build on top of atproto, about building communities with atproto.
• Mastodon posted an update about the first half of 2024 for their Patreon supporters.
• A closer look at the new features in Newsmast latest update.
• For the atproto devs: an atproto browser.
• Owncast Newsletter August 2024.
• TechLinked discusses the fediverse and how the web is different now in their podcast.
• IFTAS Connect July 2024 roundup. IFTAS is also looking for admin support while they are seeking funding to continue their work on building an opt-in content classifier to detect CSAM.
• A proof of concept for fediverse spam filtering.
• This week’s fediverse software updates.

That’s all for this week, thanks for reading!

#fediverse

fediversereport.com/last-week-…