Ilja

I understand that, but in general is there something in gsap that allows to bypass this? I am using gsap to run animations and some scroll behaviour in an ios based game built with pixi js. Being a game it doesn't feel that nice running at 30fps compared to native games that remain at 60fps. The only work around I have at the moment is playing this off as a feature and informing user that fps is capped to 30 in low power mode, but ideally it would be great to keep it 60.

@mikel Ah, listening to document event for this and toggling lagSmoothing works and makes a lot of sense actually. Just a follow up question are defaults for lagSmoothing still lagSmoothing(500, 33) as in that question, or other values should be used to re-enable it?

I assume that due to gsap using requestAnimationFrame its fps gets dropped to like 30fps when mobile device is in low power mode. I wanted to ask if there are mechanisms that would allow to bypass this and keep ticker running at 60fps in these cases?

I am working on a game that has timer that is animating down, it indicates how much time player has left to make their move. Gsap is animating this timer. Issue I am currently facing is that if player goes to a different browser tab gsap seems to stop animating the timer. After some research I believe this is by design and feature responsible for this is "lagSmoothing" I was able to disable this via "gsap.ticker.lagSmoothing(0)". However this disables lag smoothing for my whole app. I was trying to look similar method on "TimelineLite" that I am using for timer animation, but wasn't able to find anything. Hence this question: Can I disable lagSmoothing for single timeline as opposed whole app? Here is an example of how timeline lite is used in my app. import { TimelineLite } from 'gsap' const timeline = new TimelineLite() this.timeline.to(this, { /* animation config*/ })

Hey @ZachSaucier Sorry for confusion. I'll try to explain it better. First block is taken as an example of pure pixi implementation for rotation animation. I am not actually using it, however it showcases usage of "delta" (more on this latter). Second block where gsap drives pixi's ticker is what I use, it works great (I then use normal tweens to animate pixi objects). Issues start in low power mode on phones, since we are now operating in 30fps, as RAF is throttled. That first example looks more or less ok, I assume due to delta usage as its value is 1 at 60fps and 2 at 30fps, hence at 30fps it is animating faster sort of compensating for lower fps. My question is, can I do something like that in my gsap tweens or that second code example, to also speed up animations and "compensate" for 30fps drop? Both pixi and gsap in my application are set to target 60fps atm.

I am using gsap as ticker director for pixi js, as per this example https://pixijs.io/examples/#/gsap3-interaction/gsap3-tick.js I noticed that when ios device is in low power mode fps drops to 30. After some research I believe it is normal behaviour as it is related to requestAnimationFrame throttling, however animations in my app look very very choppy. In vanilla pixi, we have delta exposed to make animations faster i.e. apixiApp.ticker.add((delta) => { container.rotation -= 0.01 * delta; }); Is there something equivalent I could add to gsap's ticker to ensure animations are sped up when fps is throttled? Here is full code of how gsap updates pixi ticker pixiApp.ticker.stop(); gsap.ticker.add(() => { pixiApp.ticker.update(); });