zwitschi b551396882 docs(memory): the road is at 366 by itself, so the gap appears after Blender
Checked the obvious escape route and closed it: there are no duplicate Demo_Road_Hollywood actors after
several import rounds - one actor, identity transform, mesh Z -44..366. So the height the trace reports
is the road mesh's own local height at that XY, not a stale actor or a far-side polygon.

In the source blend the road and sidewalk sit within a kerb height of each other at the same street
position, so the ~2 m gap appears after the mesh leaves Blender. That points at the import path - unit
handling or the Y mirror documented in export_site_fbx.py - rather than the strip generation, and it is
the next thing to test.
2026-11-09 18:22:06 +01:00

Gig Line

A Linux-first Unreal Engine game about walking and driving through a real city. The first release, 0.1.0, is a walkable exterior demo around 6840 Hollywood Blvd / El Capitan Entertainment Centre, covering the south-side frontage between Highland Avenue and Orange Drive plus the north-side frontage within 50 m of the boulevard.

Status

0.1.0 is in progress. The workstation, engine, geo pipeline and project bootstrap are done and verified; a walkable DemoMap exists with terrain, street, sidewalks, kerbs and the hero façade placed from measured coordinates. Façades are still blockouts, and materials are flat colours — both are planned patches.

Current tasks are in TODO.md and the development plan is in ROADMAP.md; what was learned the hard way is in MEMORY.md.

Layout

Path Contents
Game/ Unreal project, configuration, source, game-ready content
Art/ Editable Blender sources, blockouts, terrain, street, hero façade, and a local (uncommitted) reference library
Geo/ Source manifests, permitted geographic data, and every geographic tool
Tools/ Unreal-side importers, level builders, and reference gathering
Docs/ Setup, toolchain pins, build and content pipeline, licensing, release checks
Screenshots/ Rendered review captures and their approval state

Getting started

git lfs install    # required: content, images, audio, and geo files are LFS-tracked
git lfs pull
Tools/check-lfs.sh # verifies the lfs filter is active and files are stored as pointers

The engine is installed outside the repository and pinned in Docs/toolchain.md. Setup is in Docs/setup.md; building and the content pipeline are in Docs/build.md.

Documents

Licensing

Code licence is an open decision (MIT proposed). Engine, art, and geographic data are licensed separately; see Docs/licensing.md.

S
Description
No description provided
Readme
3.1 GiB
0 Stars 1 Watchers 0 Forks
Languages
Python 84.8%
C++ 13.6%
Shell 1.4%
C# 0.2%