Repository navigation
fix(importer): retain collision when rendering colors are truncated - #691
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.
A full navigation import failed when a WMO group had a truncated terminal vertex-color chunk, even though its collision geometry was complete. The parser now omits only that terminal rendering chunk and preserves the collision bytes. Truncated collision chunks still fail.
What you verified
Synthetic tests prove that complete collision triangles survive and truncated vertices remain errors. Both full continent navigation imports completed.
Validation across the four repair commits: importer 446 passed; Module 1,698 passed; Gateway 2,172 passed; shared 310 passed; test support 15 passed; the new durable pool test passed. Importer formatting and Clippy passed. Production publish and all three full import profile checks passed.
What you did NOT verify
No new interactive client login was performed. Full workspace Clippy was not rerun locally; CI runs the repository checks.
Risk
Importer behavior changes for the described inputs. No client assets or database dumps are included.
Model and harness: GPT-6.1-sol through Codex in T3 Code.