picom VS awestore

Hello, everyone! I've been trying to set up Arian8j2's Picom fork, which has nice transition animations. Everything worked fine with opacity, rounded corners and the open-close windows transitions, but the problem is that no animation is triggered when switching workspaces, except for the fading, which comes by default from the original Picom. In the project's github page there's a gif showing the transitions, and you can see that the animations are triggered by switching workspaces. I am using these options for the transition config:

Here is link number 3 - Previous text "[3]"

Awestore - Rubato implementations often reference Awestore (specifically compatibility with it), which was last week's popular AwesomeWM animation framework until Rubato's tantra was read to the above configurations. Nonetheless, its got better documentation, sort of, and is worth a gander as it may make more sense to you or be more helpful to your purposes.

As far as compositing and animating, Awesome itself is NOT a compositor. You will need a separate compositor like picom for things like shadows, background blur, and true transparency. There are forks of picom that also implement window animations but I have not personally tried them. Simple animations can be implemented in Awesome with libraries like rubato or awestore but it's a fairly manual process of changing a window's x and/or y coordinates on a regular interval.