Hey, thanks for the tip.
I’ve done the test using “On Nearly Finished” and got same results … Works fine with Start Time = 0 but there is a gap when set it to land in a different spot in the loop …
Maybe I’m completely wrong, but due the behaviour seems “seeking the start time” happens at the same time as the “Play” and that creates the latency.
I’m assuming it works fine after the first play because it has that start point in cacheed or something …
Actually, if when it starts working properly, I go to the .asset config of the loop, and change + save a different “Loading Behaviour Override”, the gap occurs again the first time I play it.
Only if I select “Force Inline” it works fine … but I don’t have information enough on that setting to determine if this is a good workaround to be applied to all loops in the project (I’d say it isn’t :P)