You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TrailView parts P8: the old tunnel code of the new roads goes #3685
Size: M (the ground plan crate, its bridge and the viewer's shaders; mostly deletions)
Problem
After P7, the parts draw every tunnel end on the new roads, but the old tunnel code of the new roads stays in the tree: the feature bores of host/obc-ground-plan and a second copy of its height rules in the shaders. It costs shader size on the phone (#3656) and keeps two answers for one fact.
Scope
Delete the feature bores of host/obc-ground-plan: the bore faces, the cover and the lid, the shell, the end faces, in_bore, and the call of level_tags::split for tunnel ways in graph::build_with.
Delete the tunnel terms of terrain/heights.wgsl and plan/corners.wgsl, and open_max_m and body_m of data/trailview/plan.json.
Keep graph::open and the records: they hold the openings. A chain under a building only needs nothing: a shallow one is a ground way already, and another stays undrawn as today.
Activity
timohueser commentedon Nov 20, 2026
P4 (b) (#3763): what P8 finds
StructureMesh.offPlan(only today's app draws it) and the parts inplanOnly(only the ground plan draws them). When the new roads are the only path (TrailView ground plan GP19: the ground plan becomes the only path, the old code goes, docs, budgets, merge into develop #3110), both ranges and the split oftunnels(…, keep)go.partStampsofstructures/parts.ts,stamp-core.wgsl).bores:mesh/cut.rs,mesh/snap.rs,openings.rs.Generated by Claude Code