Aurora Vale: Building and Testing the First Playable Systems

An original countryside project with a testable baseline

Aurora Vale began on 3 October as an original 4,096 × 4,096 metre Herefordshire-inspired map around the River Arrow valley, Pembridge and Eardisland. The working baseline was FS25 1.24.0.0 and GIANTS Editor 10.0.13, with an isolated profile so development checks could be run without changing existing user saves.

The first layout contained 182 fields, 13 farm/village/service sites, 203 roads and access tracks, waterways and six woodlands. Subsequent changes produced a 183-field playable revision. These are historical authored-layout counts; the later geographic integration has 155 fields and three crossings.

Compact working yards, irregular cottage setbacks, hedged lanes and protected machinery access replaced broad uniform paved areas. Rural lanes were authored at 3.5–4.2 metres with passing places, while the primary road was 6.2 metres. Visual research informed the design; reference photographs were retained as references rather than copied into map assets.

Diagnosing the missing systems

• Verified historical runtime inventory: 58 placeables, 183 fields, 7 starter vehicles.
• Three positive-area animal navigation meshes; 6 production points; 5 selling-station specializations.
• Main scene and 18 original cottage/church/sign models compiled to native binary shapes; 20 visual textures compiled to BC3 DDS with full mip chains.

The first runtime exposed missing map sound configuration, invalid crop-state names, absent animal navigation meshes and a duplicate unique identifier associated with a bundled starter seeder. Named states were checked against the installed foliage definitions, the starter equipment changed and local animal configurations supplied navigation roots.

A later save contained only 42 of the expected 58 placeables. All 16 locally cloned configurations were missing. The absence of animal error messages was therefore meaningless as husbandry evidence: the husbandries had not loaded.

Moving registration into modDesc.xml did not by itself solve the runtime absence. The actual cause in the preplaced entries was the missing $mapdir$ prefix. Correcting that token and its generator allowed the expected local systems to appear in the native runtime audit.

Native vehicle details and water geometry

UK number plates required more than a FRONT/BACK material name. An externalShapesFile path using a native token did not expand as expected, so the wrapper was changed to a recorded relative copy of the installed base-game plate binary. Binary slot metadata was then authored explicitly. Native review showed a white front, yellow rear and distinct assigned registrations; the plate-edit interface remained a separate test.

Water investigation first found complete triangle coverage, so clipping was not established as the cause of the visible rims. Local-zero-height geometry and translated native-level origins were necessary but insufficient. Extending water beneath dry banks, merging the connected river/brook surface and adjusting pond excavation addressed the observed boundary.

The reviewed shoreline audit recorded zero exposed sampled edges across four water surfaces and at least 0.69 metres of dry-bank clearance. Those results describe that revision. The later real-height connected-water system required its own native compilation and review.

Gameplay evidence: harvest, transport and sale

On the earlier authored terrain, the native AI combine harvested mature owned barley field 113 to an 8,000 litre full bin. Native unloading transferred the harvested grain into the HP20 trailer: the combine measured 0 litres and the trailer 8,000 litres.

Six public bridges were crossed using ordinary keyboard driving with native tractor/trailer coupling. Controlled detached positioning was used to set up each test, followed by native reattachment and continuous driving; the loaded passes retained the full grain load. Setup assistance was recorded rather than confused with the driving result.

The ledger subsequently records physical delivery and sale of the 8,000 litres at Grain Exchange. This is stronger evidence than a sellpoint existing in XML. It remains historical proof for the earlier layout and does not certify the three revised geographic crossings or the current build’s selling workflow.

Original assets, cattle grids and regional ambience

An original grain-exchange warehouse was built in Blender 5.2.2 LTS with twin silos, hopper bottoms, legs, ladders, gutters and an open intake canopy/grate. The recorded asset contains 311 mesh objects and 5,730 triangles. Native compilation produced a 607,116-byte binary-shapes file; original Blender/geometry sources and hashes were retained. The subsequent ledger records placement of the grain exchange and original village store, with detailed operational clearance and retesting still separate.

An original 4.8 metre cattle grid used 22 rails, a recessed bed, concrete rim and a 1.66 metre bypass. Geometry/clearance tests and a clean standalone native render passed, but the recorded stage still required map placement, pit integration and vehicle crossing acceptance.

Four original, seeded ambience loops were synthesized as 48 kHz mono 16-bit WAV masters: two streams and two hedgerow rustles. Clipping, DC and seam checks were measured, with later Vorbis OGG encoding and frame-count verification recorded. These are synthesized assets rather than field recordings.

The regional authoring added 62 original spatial audio sources, constrained native blackbird/pigeon scheduling and native crow/deer selection. Seasonal weather settings used Hereford Credenhill context, with winter liquid rain and reduced snow/hail/twister weights. These are authored choices, not measured event probabilities. Audibility, seasonal scheduling, cab/interior attenuation and native weather behaviour remained runtime acceptance work.

What the first build established

• Evidence: dated entries in ledger.md; ge-toolbox-progress.md; retained native harvest, loaded-bridge and sale records referenced by the ledger.
• Current acceptance is described in the latest Aurora geography and soil entry; these results are not presented as final release approval.

A populated scene became a playable system only after runtime inventory, local registration, crop states, navigation and save behaviour were inspected. Loaded transport and actual grain sale gave the workflow concrete results to compare against future revisions.

Installed selectable DLCs and Precision Farming were included in the test profile. That establishes load coverage for the recorded combination, not exhaustive compatibility with every DLC feature. Rebuilding the terrain, roads, fields or placeable footprints invalidates relevant physical acceptance and must trigger renewed checks.