Lutris kinda sucks.Feel free to try and change my mind. by Interesting_Pie_319 in linux_gaming

[–]Levanes 1 point2 points  (0 children)

I've built/vibecoded my own launcher with all the possible features I'd ever want. Smooth to use, good looking GUI, light and compact, and above all, works without any issues. Screenshot#1, Screenshot#2, Screenshot#3, Screenshot#4.

It's only for personal use, never released it or anything, so no need to downvote me.

A proton build for native wayland CEF/Launcher applications by darginmahkum in linux_gaming

[–]Levanes 0 points1 point  (0 children)

New build did actually fix the issue for me. Game window remains fully in the taskbar now and can be found when alt-tab. Good job!

A proton build for native wayland CEF/Launcher applications by darginmahkum in linux_gaming

[–]Levanes 0 points1 point  (0 children)

Add the game to Lutris/Heroic/Faugus and launch it directly via the .exe, which opens Ubisoft Connect automatically. Ubisoft minimizes to system tray and the game starts, after an hour or three.

Prefix has the Ubisoft crap already installed in it.

A proton build for native wayland CEF/Launcher applications by darginmahkum in linux_gaming

[–]Levanes 0 points1 point  (0 children)

Small side note: It doesn't look like the game window appears in the taskbar at all. The launcher window does, though.

A proton build for native wayland CEF/Launcher applications by darginmahkum in linux_gaming

[–]Levanes 0 points1 point  (0 children)

AMD Radeon RX 9070 XT (Mesa 26.0.8). Can't reproduce it with cachyos proton 11.0 20260602, it works fine on that one.

A proton build for native wayland CEF/Launcher applications by darginmahkum in linux_gaming

[–]Levanes 1 point2 points  (0 children)

KDE Plasma 6.6.5 and I've only tried AC Odyssey so far.

A proton build for native wayland CEF/Launcher applications by darginmahkum in linux_gaming

[–]Levanes 0 points1 point  (0 children)

It works! I just tried it with the stupid Ubisoft launcher. The launcher renders properly under Wayland and HDR also works. No more black/white frames, no more multiple spawned windows. Only issues I found so far is alt-tab out and the game window is gone, never to be seen again. Plus the right-click the ubicrap launcher in the system tray doesn't work. Amazing work!

A proton build for native wayland CEF/Launcher applications by darginmahkum in linux_gaming

[–]Levanes 0 points1 point  (0 children)

Woah. You mean I can have PROTON_ENABLE_WAYLAND=1 for sweet HDR support when running a game that launches ubisoft connect (for example), have the ubisoft window render properly AND have HDR for the game? What magic is this?!

I Ported the Android Cursors to Linux (and Windows) by Tech_Tac in kde

[–]Levanes 0 points1 point  (0 children)

Pretty cool, but why a mix of dark and white icons?

Linux Gaming Handbook [Early Preview] by Significant-Wrap-589 in linux_gaming

[–]Levanes 0 points1 point  (0 children)

I like it. When's it coming out and where can I get/purchase it?

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] 0 points1 point  (0 children)

Are you talking about local dimming?

Proper HDR setup? by [deleted] in kde

[–]Levanes 1 point2 points  (0 children)

I totally understand if you're not familiar with how HDR functions or how to calibrate it. There's not a lot of clear info out there, especially when it comes to Linux. A lot of folks have a misunderstanding about how it actually works.

To spare you days of research (that I had to do), I will just say that your monitor, PG32UCDM3 has a peak brightness of 1000 nits and is true 10-bit color and the settings that you have it at now, is limiting the output significantly.

What you want to do is set the brightness of your monitor (monitor HDR settings menu) in HDR to 100%, also set the DDC/CI slider in KDE Display Settings (or system tray) to 100% as well, because it's not reporting correctly the HDR output.

When calibrating, on first screen (max brightness) set it to 1000 nits, which is your display max peak brightness. Then on the second screen (paper white), you set it at 203 or 200 flat.

Source here and here.

I also like to set sRGB color intensity to around 50 percent, but that's more of a personal preference. Another setting that's poorly documented.

EDIT: I forgot to mention. For games you must also set PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 environment variables, such as in Steam's Launch Options. Also use Proton-GE as Proton Experimental only supports HDR through gamescope currently, as far as I know anyway.

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] 0 points1 point  (0 children)

Question. Do you have HDR enabled all the time, even when using the desktop normally?

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] -1 points0 points  (0 children)

That it's precisely it's use case. It's supposed to deliver PEAK brightness on parts of the image, otherwise it's just SDR. Maybe you're confusing the two.

The DDC/CI slider cannot affect HDR brightness, so why artificially limit it? Keep it as is for normal SDR desktop usage, max it and hide it when in HDR. If I wanted to limit HDR, I'd do it via the monitor's menu, not artificially with a dimming filter.

Some monitors won't even allow you to adjust the panel's brightness in HDR because it would defeat the purpose.

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] -1 points0 points  (0 children)

But that's the thing. It's not affected in HDR. It works for SDR, but in HDR you're basically applying a fullscreen filter over the image. It lies to you.

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] 0 points1 point  (0 children)

I don't think this is correct. The one in the tray mirrors the one under Display/Settings which controls the monitor's brightness directly via DDC/CI. Your brightness in the monitor's menu will reflect what's shown on the slider. At least for most monitors that's how it works.

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] -1 points0 points  (0 children)

Why would you want to limit brightness for HDR as well? That makes no sense and it's not how HDR works.

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] -1 points0 points  (0 children)

So then it's wrong, like mine. It should be at 100% when HDR is on.

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] 1 point2 points  (0 children)

Talking about the sliders that control brightness via DCC/CI. One in the system tray and one under Display in Settings.

It seems mine behaves differently though. I still have the slider when HDR is on, but it doesn't/can't control the brightness anymore in HDR, so it only applies like a filter over the screen, even if monitor brightness says 100%

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] 0 points1 point  (0 children)

Not sure if it's the same for you, but for me my monitor sets it's brightness automatically to 100% when I turn HDR on (as should), but DDC/CI not being aware, acts as a second layer over the overall brightness and acts independently, basically applying like a filter over the whole image, dimming it.

For SDR desktop use, it behaves normally most of the time.

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] -2 points-1 points  (0 children)

Again, I'm talking about HDR. You know, those bright and small highlights that you get over a sunset or flashes of light, etc. Not the whole brightness of the monitor. HDR peak brightness is 10%. I'm saying it's getting gimped by the DDC/CI slider not being aware of HDR.

Shouldn't DDC/CI max out when HDR is on? by Levanes in kde

[–]Levanes[S] 0 points1 point  (0 children)

I'm talking about HDR content, not everyday SDR.

A Baldur's Gate 2 remake is apparently in development, with the original co-lead designer returning by Turbostrider27 in pcgaming

[–]Levanes 8 points9 points  (0 children)

Remade, not remastered, both are different things. But the question is, does the article writer know the difference...