Separate render loop from game state loop #153
Labels
No Label
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
priority:tier1-active
priority:tier2-foundation
priority:tier3-future
Refactoring & Cleanup
system:animation
system:documentation
system:grid
system:input
system:performance
system:python-binding
system:rendering
system:ui-hierarchy
Tiny Feature
workflow:blocked
workflow:needs-benchmark
workflow:needs-documentation
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: john/McRogueFace#153
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Enable "realtime" use cases via render cache. Can we enable the render loop to proceed with last-cached render state, and allow a simulation loop (owns all Python objects and execution) to run on a fixed schedule? This is a formalization of the pattern that is pretty common: a timer causing simulation updates; the problem is that requires the simulation updates to be completed in a single frame. A separate loop would permit long simulation steps while frames are updated with running animations
From john/McRogueFace/wiki/Input-and-Events.-
Providing consistent state is the challenge, but allowing event handlers to more thoroughly perform the simulation without losing frames is the reward.