earslap Posted June 10, 2017 Share Posted June 10, 2017 The regular requestAnimationFrame function is sent in a high res timestamp as an argument by the browser so that we can accurately calculate the interval between frames. This value is needed for doing fluid animations, accurate physics etc. that are not tied to a framerate. I assume that babylon renderloop uses requestAnimationFrame; is there a particular reason why this value is not exposed to the user? Is there another way / convention of getting it? Also, would it be unwise to use requestAnimationFrame directly to render our scenes bypassing the render loop of babylon? Would this have any unintended consequences? Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.