AnimationGroup.goToFrame now going to unexpected frames

This may be more of a sanity check to ensure we are using animations the appropriate way.
My team is currently using v5.0.0-alpha.60. When using AnimationGroup.goToFrame, it appears to be using a keyframe [or a frame multiplier] because calling goToFrame(2) goes to the expected second frame (possibly actually frame 48?). However, once we upgrade to any newer version, goToFrame(2) will go to the actual second frame.
Has there been a change post alpha 60 that would send a user to a different frame? Or, has the functionality of goToFrame changed since then?

There have been changes on the default animation ratio when loading GLTF files IIRC. @carolhmj do you remember the property to change ?

This was to solve this issue: Load GLTF animations at 60 FPS by default instead of 1 FPS by carolhmj · Pull Request #11945 · BabylonJS/Babylon.js · GitHub

And you can revert to the previous behavior with this code:

    BABYLON.SceneLoader.OnPluginActivatedObservable.addOnce(function (loader) {
        loader.targetFps = 1;

Fantastic. That seems like the way to go. Thank you!