Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-organize update() vs tick_update() #20

Open
g--o opened this issue Jan 19, 2019 · 0 comments
Open

Re-organize update() vs tick_update() #20

g--o opened this issue Jan 19, 2019 · 0 comments
Labels
advanced Research and develop according to JSCF's principles high priority

Comments

@g--o
Copy link
Owner

g--o commented Jan 19, 2019

Physics engine, Rigidbody, Scene and Game aren't synced on tick_update vs. update methodology.
Delta time should be configurable at runtime and callbacks should have update vs tick_update.

Should be as follows:

  • Update is roughly with periodic input/output (say music, rendering, keyboard updates, etc..)
  • Tick Update is the logic update, roughly with the different managers (physics, gui, etc..), components, entities etc. It is called after their logic is done.
  • Pre-Tick Update: Optional but can be really effective - a user tick that occures before the engine's tick.

These should allow customizability again, as manual update/render should be non-relevant as JSCF becomes an engine rather than just a library, as well as it's editor, which perhaps might be usable for meta-editing.

@g--o g--o added advanced Research and develop according to JSCF's principles high priority labels Jan 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advanced Research and develop according to JSCF's principles high priority
Projects
None yet
Development

No branches or pull requests

1 participant