Skip to content

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

@g--o

Description

@g--o

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    advancedResearch and develop according to JSCF's principleshigh priority

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions