fix(blockout): regenerate with --origin; frontage back on the verified spans
The 0.1.2 blockout regeneration ran without --origin, so Blosm centred on the extract instead of fitting the project frame. The frontage shifted ~119 m in X and ~2.4 m in Y and the hero fell outside the 6902/6838 gap - the verified placement was silently undone, while every render still looked like a plausible block. - Blockout regenerated with --origin 34.101545,-118.338718 (affine residual 0.0 cm); frontage and north buildings re-exported and re-imported. - Verified spans restored: 6922 -24276..-17700, 6902 -17749..-14591, hero -14644..-12028 between them, theatre -12082..-8210, TCL -22889..-18442, Tussaud's -27071..-22799. - ue_apply_facade_kit now uses get_actor_bounds() (world space). It had used the static mesh bounding box, which is building-line-local, so every kit piece was placed ~12 km east of its building in empty ground. - ue_import_north_buildings.py was missing 'import sys' (NameError, exit 255, import silently skipped) - the same trap as the hero importer. - Kit re-applied: 625 pieces across eight buildings; packaged QA still PASS (walk, transect 0 holes, wall probe 0/35, facade probe 0/9).
This commit is contained in:
zwitschi committed
1 parent
c9d603f754
commit
32dff056c3
48 files changed
+107
-80
No files matched your search
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Reference in new issue
Block a user