Rive Input States Persist After Reload, Causing Auto-Play Behavior

[ErsoTerso]

I’m facing a problem. I’m saving the Rive inputs to JSON so that when the game is closed and reopened, or during scene transitions, the inputs are preserved. It correctly saves any input as true, but when the game starts, it behaves as if the animation is already playing — just like in the Rive editor when the inputs are selected and the animation plays automatically. I’ll share a sample video because it’s a bit complicated.

2025-05-31-11-07-50.mp4

2025-05-31-11-08-10_1_1.mp4

[damzobridge]

Hello, I'm not sure I fully understand the issue you're referring to. Could you create and share a separate repro project that showcases the problem so that we can narrow things down?

[ErsoTerso]

I'm saving the inputs of .rive animations to JSON. During game startup or scene transitions, the inputs are triggered correctly, and the animations open as expected. However, the default state of the Rive file — the one shown before pressing Play in the Rive editor — was briefly visible.

I solved this by assigning a higher priority in Unity using Script Execution Order (SEO) to the script that writes the input values. This ensured that the inputs were applied early enough, preventing the default state from being shown.