PR to make the engine capable of hosting plugins - #1127
Merged
Conversation
3 tasks
[Feature] add render extension lifecycle hooks [Feature] add plugin-ready render graph stages and dependencies [Patch] ECS readiness [Patch] plugin-owned spatial participation [Patch] plugin asset chunk support [Patch ]Added a plugin-facing shader packaging helper [Bugfix] Fix stale XR eye context and plugin picking fallback [Patch] Add EngineExtension lifecycle for non-rendering plugins [Docs] Updated engine extension docs
untoldengine
force-pushed
the
feature/plugin_arch
branch
from
August 3, 2026 14:42
b1019ee to
2f3d4f8
Compare
3 tasks
miogds
pushed a commit
to miolabs/UntoldEngine
that referenced
this pull request
Aug 4, 2026
…dinator PR B of the physics plugin readiness plan (discussion untoldengine#1116), built on the EngineExtension infrastructure from untoldengine#1127 instead of a custom runFrame seam: - PhysicsCoordinator (EngineExtension) steps the installed backend once per fixed substep: body-set diffing against the RigidBodyComponent + ColliderComponent query, batch kinematic writes, step, batch transform read-back into LocalTransformComponent, event drain into an inert sink (subscriptions arrive in the events PR). - PhysicsBackendRegistry schedules/unschedules the coordinator in EngineExtensionRegistry on install/uninstall and locks for runtime on the first simulated substep. - Gravity for the built-in integrator now reads from the global PhysicsWorldConfiguration (default unchanged at (0, -9.8, 0)), so legacy and backend-owned bodies share one gravity. With no backend installed nothing is scheduled and behavior is unchanged; the built-in integrator keeps running legacy entities either way.
miogds
pushed a commit
to miolabs/UntoldEngine
that referenced
this pull request
Aug 4, 2026
…dinator PR B of the physics plugin readiness plan (discussion untoldengine#1116), built on the EngineExtension infrastructure from untoldengine#1127 instead of a custom runFrame seam: - PhysicsCoordinator (EngineExtension) steps the installed backend once per fixed substep: body-set diffing against the RigidBodyComponent + ColliderComponent query, batch kinematic writes, step, batch transform read-back into LocalTransformComponent, event drain into an inert sink (subscriptions arrive in the events PR). - PhysicsBackendRegistry schedules/unschedules the coordinator in EngineExtensionRegistry on install/uninstall and locks for runtime on the first simulated substep. - Gravity for the built-in integrator now reads from the global PhysicsWorldConfiguration (default unchanged at (0, -9.8, 0)), so legacy and backend-owned bodies share one gravity. With no backend installed nothing is scheduled and behavior is unchanged; the built-in integrator keeps running legacy entities either way.
untoldengine
pushed a commit
that referenced
this pull request
Aug 5, 2026
…dinator PR B of the physics plugin readiness plan (discussion #1116), built on the EngineExtension infrastructure from #1127 instead of a custom runFrame seam: - PhysicsCoordinator (EngineExtension) steps the installed backend once per fixed substep: body-set diffing against the RigidBodyComponent + ColliderComponent query, batch kinematic writes, step, batch transform read-back into LocalTransformComponent, event drain into an inert sink (subscriptions arrive in the events PR). - PhysicsBackendRegistry schedules/unschedules the coordinator in EngineExtensionRegistry on install/uninstall and locks for runtime on the first simulated substep. - Gravity for the built-in integrator now reads from the global PhysicsWorldConfiguration (default unchanged at (0, -9.8, 0)), so legacy and backend-owned bodies share one gravity. With no backend installed nothing is scheduled and behavior is unchanged; the built-in integrator keeps running legacy entities either way.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.