The First Build: Getting COGHEIM Walkable in UE5.8

Before this, COGHEIM's technical direction lived entirely in specs and conversations. The first real question wasn't "what should the engine foundation include" — it was "what's the smallest thing we can actually stand up and walk around in."

The Answer: A Walkable Slice, Not a Vertical Demo

Three options were on the table: a slice of natural disc terrain, the disc's edge, or a Iron Veil exterior blockout. The Disc Slice Foundation won — a walkable 10km×10km natural-terrain slice with a gray-box Strider on the horizon, sized as a real scale reference rather than a placeholder.

That scale reference matters more than it sounds like it should. Everything about how this world reads — how small a walking player is next to a Strider, how far a Strider can be seen before it's recognizable — depends on getting the actual meters right before anything else gets built on top of it.

What Actually Got Built

A full UE5.8 C++ project skeleton: a game mode, a third-person character with Enhanced Input, sprint, and a free camera, and a deliberately thin player controller — thin on purpose, since MAXIOM is the only diegetic interface this project uses, and a fat controller is exactly how a project accidentally grows a HUD it didn't mean to.

The scale reference itself is a dimensioned blockout actor, sized in real meters to a Grindwalker-class Strider's footprint. DefaultEngine.ini was configured for Nanite, Lumen, and Virtual Shadow Maps from the start, rather than retrofitted later.

The Bug That Almost Stopped It

The project had originally been written against UE5.4. The engine actually installed was 5.8. That mismatch showed up as a build failure: BuildSettingsVersion.V5 and EngineIncludeOrderVersion.Unreal5_4 aren't compatible with a 5.8 engine.

A second, smaller snag: Windows had .uproject files associated with Visual Studio instead of the Unreal Editor, which meant double-clicking the project opened the wrong application entirely. Worth mentioning only because it's the kind of thing that costs ten confusing minutes and isn't in any engine changelog.

What's Next

1. Enhanced Input assets — a default input mapping context and move/look/jump/sprint actions, scripted through Unreal's Python console rather than clicked through by hand.
2. Blueprint scaffolding for the character and game mode, generated the same automated way.
3. Everything after this gets built against a project that's proven it actually compiles and runs on the real engine version — not the one it was written for eight months ago.