Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
AnimationMixer finished event fires prematurely
See original GitHub issueDescription of the problem
As far as I understand it, the finished event on AnimationMixer should only fire when an action has finished.
In practice, it seems to often fire just before I’d expect.
For a 1000ms clip, at the point in time the finished fires, action.time will often be 983.4ms. This looks a lot like a single frame gap (ie 16.6ms) from the end. In addition, the property being manipulated will be just short (say, by 16.6 / 1000) of the lerp to the terminal value in a track associated with the clip.
Is this intended behavior? If so, can an event be added that only fires when the action is truly finished? If not, is this a matter of moving the location of the logic that fires the event to be a bit later in its code path?
Three.js version
- Dev
- r81
- …
Browser
- All of them
- Chrome
- Firefox
- Internet Explorer
OS
- All of them
- Windows
- Linux
- Android
- IOS
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@takahirox I wound find that much more intuitive.
Still haven’t had a chance to put together a jsfiddle showing the not-yet-final-value issue I mentioned originally, but I’ll try do that this week.
BTW, I think ‘finished’ and ‘loop’ should be fired after accumulation here.
https://github.com/mrdoob/three.js/blob/fcd6fd23b6612db1579c7d907fa0ec31156082a5/src/animation/AnimationAction.js#L377