I am running greensock animations within a WebView in an android app and I am getting random "choppi-ness".
After running tests, I am suspecting that the frame pace of the Android app and the pace of the greensock timeline are out of sync.
This may be causing an animation to last longer than a frame and causing jumpiness in the animation.
The GPU performance is showing that the animation frames are taking less than 16ms to render but still a visual chop to the animation.
Has this ever been explored?
I could be way off base for the cause of the chop but I have done "force3D" to force it onto the gpu and I am certain the code is right since it does clear up in a normal browser, however, there isn't a significant change in the Android WebView.
https://developer.android.com/games/optimize/frame-pacing