I’d like to add that the current Cosmic DE in use is an ageing fork of Gnome and is going to be replaced with a Rust-based DE called Cosmic (Epoch) soon.

Correct. Your GPU is probably just really fast.
NVK is going to be killer on your system.

If you’re using AMD, you probably have ACO compilation which tends to be much faster than LLVM.
For me I use pre-compilation + ACO + DXVK Async so it compiles and cache super quickly.

It’s usually disabled outside of steam. However you can use environment variables :

DXVK_ASYNC=1
DXVK_STATE_CACHE=true
DXVK_SHADER_CACHE=true
DXVK_STATE_PATH=
DXVK_STATE_CACHE_PATH=

Turning it off just pushes the shader cashe-ing to runtime. You might have micro stutters, but it’s temporary as things get cashed as you play.

man kscreen-doctor
kscreen-doctor -o

Neither of mine support HDR and I still get the option.

Definitely needs a bug report.
I recommend go into Wayland and use hw-probe and run :
sudo -E hw-probe -all -upload -dump-acpi -decode-acpi
And use the given link in your BR.
Try to force the bug, and take a screenshot or if it doesn’t show up in the screenshot take a picture with your phone and mention it doesn’t show up in screenshots.
If you’re able to consistently reproduce the bug include how.
Make the BR to Kwin.

What’s your GPU?

Found the option, and you’re right. It’s currently not available on Wayland.

Window shade?

Vox-libre

One fun one is to pipe clipboard to qrencode — it’s a simple and (nearly) universally supported way of getting a URL, etc., from a laptop/desktop to a phone.

KDE Connect

Make sure to share your tips and tricks guys!!

It’s the car manufacturers failure when they can’t properly put their tires on to safely drive on the road or put on tires that weren’t up to code to begin with.

I don’t see any graphical glitches on my hardware.
Perhaps you’re still on the qt5 version?
Maybe a bug with your Nvidia driver?
Perhaps your WM doesn’t have explicit sync yet and your card & driver needs it in this particular case? Perhaps it’s running under XWayland?

Wayland#Qt :
While it shouldn’t be necessary, to explicitly run a Qt application with the Wayland plugin, use -platform wayland or QT_QPA_PLATFORM=wayland environment variable.

As it says above, it should really be inferred by default. Something weird is going on here.

Cura as in this one? :

You miss the entire point of WMs then.
You’re complaining about 7 lines of configs when the entire point of WMs is for you to literally customize everything through configs.
Shit, you probably don’t even need half of that crap. QT_QPA_PLATFORM=wayland is already handled by qt, you only need that when running apps across Waypipe from a headless server environment. By default QT infers your environment from $DISPLY which is always :0 in Wayland.

Here’s just a tiny fraction of the Nvidia specific bugs on X11 :

https://github.com/NVIDIA/open-gpu-kernel-modules/issues/380

https://bbs.archlinux.org/viewtopic.php?id=283461

https://forums.developer.nvidia.com/t/16-bit-overlays-broken-with-x11-and-4xx-series-driver/128067

https://bugs.kde.org/show_bug.cgi?id=460341

labwc

You’re using a WM bud, wtf do you expect?

If Nvidia had worked together on Xorg, we wouldn’t have had all of those shitty Nvidia unique x11 bugs with Nvidia’s crappy proprietary drivers in the past.