Stuck on an issue?

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.

animatable.goToFrame bug when animatable.speedRatio is !== 1

See original GitHub issue

Hi,

First of all, I’m new to Babylon.js and WebGL in general. So I might be wrong or missing something here 👼

I do have a simulation running with Babylon and within the “player” I can select the exact time I want to go to by clicking on a “timeline”.

It works great! But the thing is, if the animatable.speedRatio is different than 1, it’s going to a (random?) wrong time.

I’ve just added a simple console.log before calling animatable.goToFrame: No matter what’s the current speed ratio, if I click at the same spot, it’s calling animatable.goToFrame with the same (good) value.

Here’s why I believe it’s a bug from Babylon.js and not the app.

Issue Analytics

State:
Created 6 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

zakhenrycommented, Feb 5, 2018

@deltakosh I’ve had a go at a repro, and I believe this covers it:

https://www.babylonjs-playground.com/#JYIUDS#1

I’m not convinced that the speed ratio is actually at fault, as there appears to be an issue even when not changing the speed ratio, but setting it on init to a value other than 1

0reactions

deltakoshcommented, Feb 5, 2018

Will check it asap! Thanks a lot