fix: increase cinematic scroll frame resolution - #8
Merged
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
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.
Summary\n- Increase the scroll cache from 12 to 24 sampled frames per second (up to 240 frames), keeping the approximate bitmap pixel/memory budget flat by reducing cache width.\n- Keep the stable bootstrap sprite visible until the complete dense cache is extracted, avoiding a partial-cache handoff.\n- Strengthen continuity/cadence evidence for bootstrap, cached scrolling, and repeated reversals.\n\n## Verification\n- typecheck, lint, design lint, asset validation, and production build passed locally.\n- Focused browser evidence passed on the local build, including all four cinematic routes, reduced motion, warm-up continuity, and fine-scroll cadence.\n- Production baseline confirmed 120 cached frames over a 10.04-second source (~12 samples/s), motivating this narrowly scoped correction.\n\nThis does not change page structure or visual design.