You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2023. It is now read-only.
Right now the execution tick is done by the Korio's eventLoop request animation frame.
In JVM it is implemented at 60fps while in browser depends on the implementation. So in one places it will run at 30fps, other 60fps or 120fps for example in chrome with a screen with a 120hz refresh rate.
Also asynchronous code can defer some code to the next frame, that can cause things like lowering the fps to the half, to a quarter and similars.
Also GE -> GPU should be as fast as possible instead of once per frame. In other case render targets will be renderer just half the time and will cause the same problem related to half-ing the frame rate.
Design a proper way for executing things so it works consistently between implementations and do not lower the framerate.
The text was updated successfully, but these errors were encountered:
Right now the execution tick is done by the Korio's eventLoop request animation frame.
In JVM it is implemented at 60fps while in browser depends on the implementation. So in one places it will run at 30fps, other 60fps or 120fps for example in chrome with a screen with a 120hz refresh rate.
Also asynchronous code can defer some code to the next frame, that can cause things like lowering the fps to the half, to a quarter and similars.
Also GE -> GPU should be as fast as possible instead of once per frame. In other case render targets will be renderer just half the time and will cause the same problem related to half-ing the frame rate.
Design a proper way for executing things so it works consistently between implementations and do not lower the framerate.
The text was updated successfully, but these errors were encountered: