It simply works for me. My desktop is on Debian sid, running GNOME 41.0 on Wayland with dual monitor setup 3840×2160 and 1920×1200 on AMD graphics, and everything just works. I did deliberately buy AMD graphics because of the support.
Laptop is also on sid, with Intel graphics and 4k display and there absolutely no issues there too. I don't see any blurriness in vscode or any other application that I use. But also, I'm not using a lot of graphical apps. Mostly it's just Firefox, vscode, android-studio, tilda, and sublime-merge.
Sorry, it's tilix, not tilda.. used tilda for years until I got used to tilix and the splitting. I'm still missing the quake mode that's unavailable under wayland.
Comments
It simply works for me. My desktop is on Debian sid, running GNOME 41.0 on Wayland with dual monitor setup 3840×2160 and 1920×1200 on AMD graphics, and everything just works. I did deliberately buy AMD graphics because of the support. Laptop is also on sid, with Intel graphics and 4k display and there absolutely no issues there too. I don't see any blurriness in vscode or any other application that I use. But also, I'm not using a lot of graphical apps. Mostly it's just Firefox, vscode, android-studio, tilda, and sublime-merge.
[edit] Looks like this: https://imgur.com/a/Zcc031e
How are you using tilda on Wayland, i.e. without global hotkeys?
Sorry, it's tilix, not tilda.. used tilda for years until I got used to tilix and the splitting. I'm still missing the quake mode that's unavailable under wayland.
The compositor (mutter) provides support for global hotkeys.
Do you re-open a running tilda instance? Or open a new one every time you press the hotkey?