Optimize v0.40 motion, performance, and world framing - #13
Merged
Conversation
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.
Summary
Performance
Medium preset, four production views, 6 second measured windows:
World integrity and motion acceptance passed in every view. The report's only red budget item is expected: the authored medium preset deliberately renders at DPR 0.60 while the generic benchmark budget requests DPR 1.0.
Validation
npm run typechecknpm run lintnpm run format:checknpm test -- --reporter=dot --maxWorkers=2, 103 files and 1016 tests passedVERSION=v0.40 npm run buildnpm run validate:bundlenpm run validate:uncrewednpm run validate:releasesnpm run validate:assetsnpm run validate:depthnpm run validate:shadersnpx impeccable detect src