zwitschi
f681d83736
Used the workflow integration from the previous step for real: generated a warm limestone ashlar albedo with two profiles compared (AlbedoBase 17.04 vs Krea-2 13.90, AlbedoBase won), saved it as Art/textures/generated/T_FacadeAshlar_AI.png beside its provenance sidecar, and imported it to /Game/Hollywood/Textures. ue_hero_facade_import.py now imports that albedo and, for the two stone slots, builds a material with TextureSampleParameter2D -> Multiply(tint) -> Base Color, tiling the UVs 6x, so the map carries the coursing and the tint keeps the value inside the reference's range. Two real bugs fixed on the way: - the albedo path was resolved against unreal.Paths.project_dir() (Game/GigLine), not the repository root, so the import silently skipped; - the authored materials were never saved - only the mesh was - so after a reload the slots pointed at nothing and the elevation fell back to one default colour. Honest status: the nodes are verified present and saved (Constant3Vector, TextureSampleParameter2D, TextureCoordinate, Multiply) and the source mesh has UVs, but the render still shows the flat tint. Recorded in TODO.md with the next probe: read the compiled Base Color pin instead of the node list. THIRD_PARTY_NOTICES.md gains the AlbedoBase row (commercial use, credit required).
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
.blendsaves 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.
.blendfiles are LFS-tracked and lockable; pull before editing.