0 Fork 0

Files

T

zwitschi 160e9144f9 fix(hero): export smoothing groups; give the facade real collision

UE export hygiene (unreal-export skill checklist) plus a gameplay defect the new
probe caught:

- FBX export now uses mesh_smooth_type="FACE" (was OFF, which is why every import
  logged "No smoothing group information was found"), and the round parts are
  shaded with shade_smooth_by_angle(35 deg) before export, so columns and
  medallions read round instead of faceted.
- SM_HeroFacade had complex-only collision, so capsule sweeps and line traces
  passed through the wall: the player could walk through the hero facade.
  auto_generate_collision was tried and rejected (coarse hulls bulged into the
  street; the QA wall probe went 0/35 -> 2/35). It now uses UseComplexAsSimple,
  saved on the asset, like the terrain.
- New -qaselftest facade occlusion probe: 40 m traces sideways from the road
  centre at walking height, required only where a building is staged (explicit X
  spans mirroring ue_build_demo_map). Result 0/9 -> PASS, alongside transect
  0 holes and wall probe 0/35.

Docs: release-checks records the probe and both collision attempts; Tools/README
lists the new phase; MEMORY records the smoothing/collision lessons.

2026-11-08 17:53:31 +01:00

GigLine

fix(hero): export smoothing groups; give the facade real collision

2026-11-08 17:53:31 +01:00

README.md

chore: scaffold repository and record 0.1.0 setup state

2026-11-06 21:20:57 +01:00

README.md

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 checks
Source/ — C++ modules
Content/ — 0.1.0 map, materials, meshes; LFS-tracked
GigLine.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.