Log of bugs I run into

[nuxttux]

Hi, In order to avoid making multiple post for bugs or certain questions, I'll post them here. I don't know what to make of this first one.

Using Friction RC2 AppImage on Linux Mint 22.1.

Bug 01:
The project has two scenes. The first scene is COMP 1 and the second scene is Render COMP

I linked COMP 1 to the Render COMP. Then I got a series of error pop-ups. (Errors related to expressions used in rig).

The rig still works inside COMP 1. I got the error a few times, even without linking the scenes - I was testing a shader and I also got the error.

Bug 02:
After linking the COMP 1 scene into the Render COMP scene, I applied Frame Remapping to it and push the end key-frame forward in time.

When pushed 2+ seconds forward, it results in the eyebrows of the animated character to de-synchronize with the rest of the animation. Only the eyebrows, which are both paths, and are animated using the paths property.

If pushed 1 second forward, they eyebrows remain synchronized, visually. I do not know if it's 1:1 frame wise.

[Nothing major so far - besides a few random crashes.]

[nuxttux]

Bug 03:
This one is more of a naming convention which adds an extra step when creating expression using "Sub-path effect".

If you want to call-out a property inside the Sub-path effect in an expression, the hyphen interferes.
Luckily, you can change the effect name, so you can manually remove the hyphen.

I've attached an image with one line using the default name which doesn't work, and one line where I changed the name to get it to work.

[nuxttux]

Bug 04:
Expression break during animation.

I've experienced this breakage in multiple projects by now.

In the following example I applied a transform effect -> follow path on a Null (null object).
I then applied an expression on the complete value of the Follow Path to link it to the offset value of the sub-path effect (renamed subPath) inside of Outline base effect of Body.

The Head is parented to the Null (null object).

If I manually adjust the offset value of the sub-path effect the Null, set to follow path, follows the path and remains synchronized.
However, the moment I add a key-frame, the Null gets de-synchronized with the path.

Notice that it syncs as soon as I delete the key-frames. This happen with or without Preview cache.

I experienced something similar with the L_arm of this animation project

Side note: Is the stroke taper effect on the Friction roadmap?

Example of Bug04:

friction_bug04.mp4