Apex GP

Devlog

Grass that stopped popping, and a bake that was lying about the sun

Grass stopped popping in a ring around the car, a baked lightmap turned out to have been baked on a detached scene, and a failed renderer trial stopped being retried.

The grass had a visible ring in it: driving toward the horizon, the lawn changed character in a circle around the car. It was three separate faults. The mid layer was lengthening blades by 1.9x, so the middle distance stood at 6.2 cm against 2.7 cm at the wheels. The near-cell and cluster swaps changed the layout in one step. And the far layer started exactly at the verge edge. Every hand-over is a band now, not a circle: each instance picks its own distance across a spread of metres, pulled in by a slow noise, and near blades shrink away by their own radius over eight metres of travel. Counted pops within 140 m of the car went from 24,677 to 0 across five graphics configurations. Blades ended at 2.0 cm, and verge clumps at 10.0 cm mean and 16.6 cm tallest, down from 24.6 and 40. The same pass stopped planting grass on near-vertical runoff-strip faces: 30 of one circuit's 11,951 strip quads had tufts under the tarmac.

A bake that was lying about the sun

The expensive one was baked lighting. A bake produced shadows that were wrong in a way I could not explain, and a CPU ray over the same geometry explained it in one run: the editor reopens the last session's scenes and makes one current about 150 frames after start-up, so the bake had run on a detached copy where every transform read as identity. Every mesh sat at its own origin under a horizontal sun. The road's shadowmask read 43.7% sunlit; the ray read 99.8%. The baker now waits for the bake scene itself to be current, refuses a bake it cannot verify, and fails itself if under 85% of road users are sunlit. Rebaked, the mask reads 99.9% against the ray's 99.8%. It still does not ship: with the ambient matched it is a wash on asphalt, and its one visible effect is a gantry shadow the cars never receive.

The optimiser stopped lying to itself

A Forward+ trial that fails is now final on that device: nothing automatic measures it again, and Optimise Now on a failed renderer carries the request to the next Mobile start. The trial was also handing back settings it borrowed - its ladder's cheapest rung was saved as the player's own, so a High preset at 81% came back as Custom at 50%. The arm step snapshots those keys now and the revert restores them.

← All devlog posts ยท RSS