Repository navigation
Compute animated Item Display poses directly - #42
Merged
Merged
Conversation
Interpolating parts get their pose from vanilla's orientation and interpolated transform times a rest learned from the last vanilla pose, instead of a full vanilla submit every frame. A part takes this path only after its rest predicted a vanilla pose; others keep the ordinary path. A new setting controls it, ON by default.
This was referenced Nov 5, 2026
Merged
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
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.
Problem and resulting behavior
About two thirds of Live geometry parts on a ModelEngine spawn are interpolating. Each of them ran the whole vanilla
submitevery frame just to get its pose: the largest single cost of Live capture.Transformation, times a rest matrix learned from the last vanilla pose.live_posesbenchmark target in the add-on, andposeFast,poseRejected,poseChecksandposeMismatchesin the Live geometry diagnostic.Validation performed
./gradlew spotlessApply build(JDK 25.0.4): passes, with 43 local JUnit tests. English and Russian translation key sets are equal.LivePoseFastClientTest(new),LiveViewCullingClientTest,LiveDisplaySceneClientTest,LiveExtractionSceneClientTest,StaticDisplaySceneClientTest,TextAndLiveSceneClientTest,FeatureBatchLiveClientTest,DrawLessSettingsClientTest,DisplayProbeClientTest,BenchmarkSeriesClientTest,ItemMeshEvictionClientTest,PlayerArmorClientTest,PlayerItemClientTest,IrisShaderPackClientTest.LivePoseFastClientTest: 16 animated displays with every billboard mode, entity rotation, negative scale, item transforms and one riding another entity. A test-only mode compares the predicted pose with vanilla's on every frame: 960 to 2864 comparisons per run, no mismatch. With the option on, all 16 take the direct path, and the final frame matches a fresh vanilla capture pixel for pixel.LiveDisplaySceneClientTestnow accepts either the vanilla or the direct path for its interpolating display.The series measured +0.99, +6.23 and +5.40% (mean +4.20%), but the OFF phases varied by 7.96%, so the FPS figure is not reliable. From the saved work, about 0.055 ms of a 3.3 ms frame, I'd expect about 2%. I looked at animated NPCs up close with the option on and didn't notice anything unusual; that is an observation, not pixel parity.
Limits and compatibility
One scene and one session; GPU time not measured; crowded scenes not measured. Pixel comparison uses simple models, while the field run covered real multi-part models only through the pose check. The rest matrices add one
Matrix4fper tracked instance. With an Iris shader pack active, Live geometry is paused, so this path is unused.