dual_kawase Blur does not work with --backend glx

[gardotd426]

Platform: ArcoLinuxB 20.4.10

GPU, drivers, and screen setup: Sapphire Pulse Radeon RX 5600 XT, rounded corners fork of i3wm, dual monitors set up with xrandr.

Compton version: vgit-c67d7

Compton configuration: https://pastebin.com/MWthVngz

Steps of reproduction

In i3, try using dual_kawase blur with glx backend.

Expected behavior

According to the README.md here at this fork, dual_kawase blur "only works with --experimental-backends and --backend glx". However, with glx set either at runtime through --backend or in the picom.conf config file, there is zero blur. Transparency still works, so picom itself does in fact launch, but there's no blur whatsoever.

Current Behavior & Other details

With --experimental-backends, dual_kawase DOES in fact "work," but there are so many glitches and artifacts and just plain ugliness, that it's unusable. Here are a couple examples, one is of a terminal, and another is of this very window I'm currently typing in:

Pretty much every window that doesn't have focus looks like this, and I've tried killing and restarting it multiple times. So I wanted to try glx as the backend to see if that helped. The glitches go away, but there's zero blur.

[tryone144]

According to the README.md here at this fork, dual_kawase blur "only works with --experimental-backends and --backend glx". However, with glx set either at runtime through --backend or in the picom.conf config file, there is zero blur. Transparency still works, so picom itself does in fact launch, but there's no blur whatsoever.

dual_kawase is only implemented for the experimental glx backend, as in "it only works with --experimental-backends AND --backend glx" (logical and, i.e. you need both 😉).

If --log-level is set to WARN or below, you could see the warning "Old backends only support blur method 'kernel'. Your blur setting will not be applied".

With --experimental-backends, dual_kawase DOES in fact "work," but there are so many glitches and artifacts and just plain ugliness, that it's unusable. Here are a couple examples, one is of a terminal, and another is of this very window I'm currently typing in:

[snip]

Pretty much every window that doesn't have focus looks like this, and I've tried killing and restarting it multiple times.

These screenshots look terrible, there is clearly something wrong. Could you please test the experimental backends with a minimal config (no blur) to help isolate the issue?

$ picom --config /dev/null --experimental-backends --backend xrender
$ picom --config /dev/null --experimental-backends --backend glx

[gardotd426]

Sure thing. It's early here, when I'm fully awake and stuff I'll be happy to test out that stuff for you.

[zorjo]

Also,changing the blur strength at while compositor is running, though the .conf file, causes the blur to stop, and there is full transparency until I restart the compositor

[tryone144]

Can you re-check with a clean build from https://github.com/tryone144/picom/tree/feature/dual_kawase?
This is the PR-branch rebased against the current picom head.

Sadly I can't reproduce this with with my nvidia-based setup.

[gardotd426]

Sure thing

…

On Sun, Jul 12, 2020 at 4:37 PM Bernd Busse ***@***.***> wrote: Can you re-check with a clean build from https://github.com/tryone144/picom/tree/feature/dual_kawase? This is the PR-branch rebased against the current picom head. Sadly I can't reproduce this with with my nvidia-based setup. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM5Y33Z577A7WBJL26FLIDTR3INJZANCNFSM4MGEELPQ> .