Skip to content

Complete island surface quality and fix camera pacing regression - #401

Merged
Nauxie merged 27 commits into
mainfrom
abhinav/fix-severe-camera-regression
Jul 17, 2026
Merged

Nauxie merged 27 commits into
mainfrom
abhinav/fix-severe-camera-regression

Conversation

@Nauxie

@Nauxie Nauxie commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Summary

  • complete the authored island surface and hero-landmark quality pass across all 41 islands
  • fix the severe camera-feel regression by bounding runtime materials to palette families, restoring display-synchronized presentation, clearing inactive mouse history, and removing oversized hero camera blockers
  • add material, frame-time, slow-frame, continuity, and base-vs-candidate regression gates
  • update the evaluation contract and project status with measured root-cause evidence

Root cause

The surface pass increased live materials from 100 to 244, raising full-content average frame time from 9.77 ms to 15.63 ms. Palette-family reuse restores the same 1.23M-triangle scene to 116 materials and about 8.6 ms. An attempted AutoNoVsync mitigation was also rejected after measuring worse 14-16 ms pacing on the validated Mac; the play window now explicitly uses display-synchronized presentation.

Verification

  • cargo fmt --check
  • cargo check --all-targets
  • cargo clippy --all-targets --all-features -- -D warnings
  • cargo test --all-targets --all-features
  • camera continuity gate: 13/13 scenarios, including fault-injected snap rejection
  • development performance gate: debug 8.6400 ms average, release 8.6304 ms average, 116 materials, 1,228,832 triangles
  • world content gate: all 41 islands and 123 hero views passed

@Nauxie
Nauxie merged commit e5d4439 into main Jul 17, 2026
1 check failed
@Nauxie
Nauxie deleted the abhinav/fix-severe-camera-regression branch July 17, 2026 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant