Files
gig-line/Art
zwitschi d0d87e8fda fix(site): the slice cuts now keep the middle, and the surfaces do not agree
Two findings, one a bug and one the real cause.

Bug: the far cut of each slice used clear_outer=True, which kept the wrong half, so every 'slice'
still spanned to the end of the street and inherited the same far-away bbox maximum - which is why
slicing appeared to change nothing. Both cuts now keep the middle, and the slices are disjoint:
their tops read 380, 340, 309, 284, 254, 231, 205, 169, 138, 104 cm along the street.

Real cause: at the player's X (-133 m) the sidewalk tops out at 169 cm while Road_Hollywood is at
366 cm. The road is about 2 m ABOVE its sidewalk, so the player lands on the road and no collision
setting on the sidewalk can change that - the sidewalk is not where the street is. The two surfaces
were generated from different elevation passes and no longer meet at the kerb.

That is site-pipeline data, not placement. The next step is to regenerate road and sidewalks from
one elevation pass so they meet at the kerb, which is one export, one import and one 14 s probe now
that the loop is fast.
2026-11-09 18:19:39 +01:00
..

Art

Editable sources and original textures. Exported, game-ready output goes to Game/Content/.

Layout (as content arrives)

Path Contents
Art/blender/ .blend sources, one file per building or asset family
Art/textures/ Original texture sources before baking or compression
Art/reference/ Reference photography, local only, gitignored — never committed. Fetch with Tools/commons_fetch.py; what it is evidence for goes in Docs/reference-notes-hollywood.md

Rules

  • Every .blend saves with a real-world metric scene scale. No exceptions; scale drift is the main source of import defects.
  • Named export presets only. Record the preset name and its settings next to the asset that used it.
  • Textures enter as a documented source (author, licence, source URL) and are listed in ../THIRD_PARTY_NOTICES.md.
  • Reference photography is never committed and never shipped. It is evidence, not content. Licensing is not a gate for local private development, but anything that would derive from a reference in a shipped asset needs a licensing decision before release.
  • .blend files are LFS-tracked and lockable; pull before editing.