Skip to content
This repository has been archived by the owner on Jan 29, 2023. It is now read-only.

Proper implement thread stepping and synchronization #7

Open
soywiz opened this issue Nov 21, 2017 · 1 comment
Open

Proper implement thread stepping and synchronization #7

soywiz opened this issue Nov 21, 2017 · 1 comment

Comments

@soywiz
Copy link
Member

soywiz commented Nov 21, 2017

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.

This was referenced Dec 1, 2017
@soywiz
Copy link
Member Author

soywiz commented Dec 2, 2017

We have to synchronize gpu rendering in a way that works on JS and JVM.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant