Skip to main content
16d ago

The Latest Flutter Runtime Does Not Support "Capture Base State" Property

Context:
I am using "Blend" to define the range of "Input" values, allowing developers to precisely control the timeline by adjusting the Input.

Issue:
When Flutter developers assign values to the Input after compilation, the resulting animation does not match the effects I see in the editor. Specifically, the animation in the Flutter application appears offset relative to the Input values.

Tests Conducted:
We tested the animation and Input using the web version (with the latest web runtime dependencies), and it worked correctly without any issues.

Suspected Cause:

  • In the Editor: If "Capture Base State" is enabled, the timeline in the editor behaves correctly, with no offset (as expected). However, if "Capture Base State" is disabled, the timeline becomes offset, causing a mismatch with the Input values.

  • In Flutter Runtime: Regardless of whether "Capture Base State" is enabled or disabled when exporting the RIV file, the Flutter Runtime always shows the timeline as offset. In other words, even if "Capture Base State" is enabled in the editor, it seems like the Flutter Runtime ignores this setting and behaves as if "Capture Base State" is disabled.

Summary:
Could this issue be due to the latest Flutter runtime dependencies not supporting the "Capture Base State" property?
If so, do you plan to update the Flutter runtime dependencies to support this property by January?

3 replies
15d ago

That sounds like a potential bug in the Flutter runtime. I'll get an engineer to take a look. In the meantime, I have a solution for you:

  1. Create a new state machine layer to the left of Main

  2. Add the 00_idle_0_ timeline to that state machine layer

Adding this will do the exact same thing that "capture base state" should be doing.

14d ago

Oh!! Thank you for sharing the solution—this method does work!
I still hope that future versions of the Flutter runtime can natively support the 'Capture Base State' feature, as there might be many other users who are unaware of this workaround.

12d ago

I chatted with the engineers who manages the Flutter runtime and he's going to get that working. Thank for reporting this!