Xwayland doesn't get input in some special way, it uses the exact same Wayland protocols to get input events as native Wayland apps. All claims about it being more complete or anything like that are nonsense.
Krita forces Xwayland because they have some X11 specific code they haven't bothered porting away from, that's all.
What kind of flickering? Does the display support adaptive sync? If so, try turning that off
You don't need to use steamtinkerlaunch, putting gamescope --hdr-enabled --fullscreen -W width -H height -- %command% into the launch options is enough.
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?
Gamescope can't make a different compositor support HDR. Until Gnome supports HDR and the protocol used by gamescope, it won't work.
Closing the window during an update is supported, you don't have to worry about it. Discover continues running in the background, and shows a notification until the update is complete.
For Netflix there's a browser extension that does it, but I don't know of a solution for other streaming services
I wouldn't read that much into it. Valve isn't Nintendo, I doubt they'd launch a new Deck without OLED
That is not NATO starting any war, anyone wirh the reading comprehension of a six year old understands that. Don't fall for Russian propaganda, FFS.
Quite the opposite, bigger grids are much more stable. When faults happen, tiny subsets of the grid get disconnected from the rest, it does not take the whole thing down at all...
Yeah, it gets more blown out the bigger the difference between the sdr brighrness setting and the highlights is.
Support for HDR screenshots is hopefully something I can add soon-ish
How are you taking the screenshots? Spectacle might not capture HDR highlights well, but it should look all proper on SDR content
Also, your blog is fantastic, I'm always happy when there's a new post =)
Thank you, I'm glad you like it!
I feel like in SDR mode, the OLED is pushing brighter images. I almost feel like it's underselling the capabilities at 270, but does so to give pixels a rest every now and then, in the hope that the bright spots don't stay stationary on the screen. It's a wild guess, I have no idea.
It's certainly possible, displays do whacky stuff sometimes. For example, if the maximum brightness in the HDR metadata matches exactly what the display says would be ideal to use, my (LCD!) HDR monitor dims down a lot, making everything far, far less bright than it actually should be.
KWin has a workaround for that, but it might be that your display does the same thing with the reported average brightness.
That's a terrible example, because they completely ignore the many many years old standardized APIs (screen casting and remote desktop portals) that they could use, in favor of doing hacky and broken things that require root access instead.