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).
Game
The Unreal project lives at Game/GigLine/GigLine.uproject once created. Nothing here yet.
What gets committed
Config/— engine and project settings, including the quality presets used for release checksSource/— C++ modulesContent/—0.1.0map, materials, meshes; LFS-trackedGigLine.uproject
What does not
Binaries/, Intermediate/, Saved/, DerivedDataCache/ — all generated. .gitignore covers them; do not add exceptions.
Engine
Installed outside the repository. Its path and exact version are recorded in ../Docs/toolchain.md. Nothing in this directory may assume a machine-specific engine path; the documented build procedure is ../Docs/build.md.