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 not really a Wayland thing, that’s an (apparently badly implemented) attempt to bridge X11 apps to a permission system they were never written for.
With appropriate sandboxing of apps so they can’t just LD_PRELOAD code into all other apps you run, yes.
I understand that it’s an absolute brightness standard, not like the relative levels in SDR
The standard is also relative brightness actually, though displays (luckily) don’t implement it that way.
why does it end up washing out colors unless I amplify them in kwin? Is just the brightness absolute in nits, but not the color?
It depends. You might
Why does my screen block the brightness control in HDR mode but not contrast?
Because displays are stupid, don’t assume there’s always a logical reason behind what display manufacturers do. Mine only blocks the brightness setting through DDC/CI, but not through the monitor OSD…
Why is my average emission capped at 270nits, that seems ridiculously low even for normal SDR screens as comparison
OLED simply gets very hot when you make it bright over the whole area, the display technology is inherently limited when it comes to high brightness on big displays
Multi monitor VRR has never been problematic in Wayland, but the NVidia kernel driver doesn’t support it at all yet, Xorg or Wayland doesn’t matter.
Yes, and many distros have a polkit rule set up to allow installing or updating without a password. You can likely just copy it from Fedora or sth
Writing graphics code in a unified model is quite a bit different from the conventional x86 model.
It isn’t. The difference is pretty small, and it’s just optimizations for when copies can be skipped and not a radical change in the approach of how rendering is done.
Intel would need their own equivalent to Metal if they wanted to do a similar move.
Not at all. If big-ish changes were required, they could be exposed as Vulkan extensions.
I don’t know enough about Vulkan to say if it’s compatible with this kind of approach
Of course Vulkan, the graphics API used on all modern phones except Apple’s, supports using integrated graphics efficiently.
S3 is standby. Hibernate is S4
the fact that 1.8 was working tells me that it is possible for a window manager to work well for nvidia
Nope, it’s a race condition for which the visible effects can appear or disappear for plenty of reasons. The only fix is explicit sync, which is being worked on for wlroots
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.