It probably makes sense that the clock runs off of the same requestAnimationFrame scheduling as the renderer. With the merging of #671 this is no longer the case and may cause some stuttering in LFO based animations.
To implement this we either inject some raf implementation to the clock or we rework how the clock is used and consumers of the clock have to keep it updated by manually calling tick every frame.
There are probably other plugins also affected by this, although that may be solved once we have plugin.update implemented (#664)
It probably makes sense that the clock runs off of the same requestAnimationFrame scheduling as the renderer. With the merging of #671 this is no longer the case and may cause some stuttering in LFO based animations.
To implement this we either inject some raf implementation to the clock or we rework how the clock is used and consumers of the clock have to keep it updated by manually calling
tickevery frame.There are probably other plugins also affected by this, although that may be solved once we have
plugin.updateimplemented (#664)