Devlog · tag
unreal-engine-5.8
18 entries tagged “unreal-engine-5.8”.
-
Claude Code desktop app closes instantly on launch — and Windows "Repair" doesn't fix it
The Windows app exited on its own and then refused to open at all; three plausible fixes (Windows repair, pruning a 6 GB session-history folder, a GPU setting) all did nothing, and the real cause turned out to be the app restoring a saved in-app browser preview pointed at a local dev server.
-
The agent's memory got too big to load — and it failed silently
A week of compacting, restructuring and pruning an AI coding agent's memory, including the night the whole knowledge store was archived by accident and came back only because one session went looking for one note.
-
The toilet minigame is finished, verified, and nobody has played it
A pub cleaning job built on top of a toilet minigame reached eight-of-eight phases and passed a live in-editor test measuring exactly the predicted numbers — and a pre-test adversarial audit had already found six critical defects that every automated check in the project called clean.
-
The score improved every round and the fault never did — the quality gate excluded the neck and the arms
A police uniform's torso was rebuilt for a fortnight while an automated coverage score kept improving and the same holes kept appearing around the neck — because the gate filtered out the two regions being complained about.
-
Far too harsh on the keyboard — the ebike's steering had no smoothing
A digital keypress was assigned straight to the steering axis, so the bike went from zero to full lock in one frame; here is the fix, a headlamp that came on three hours after dark for an unrelated reason, and an honest note that nobody has ridden any of it yet.
-
Getting a MetaHuman from four sessions down to one
The end-to-end route from a reference photo to a dressed, animated NPC in Unreal 5.8, and the traps that had to be paid for one at a time before it became repeatable.
-
Ten cabs, one road graph, and the bugs only a fleet could find
Building a working taxi firm — book from the in-game phone, ride in the back, pay on arrival — and the failures that a single test vehicle had hidden for months.
-
The singer who is on at eight, and the mic she never put down
Building a live turn in the pub — an NPC who leaves the bar, sings for an hour of game time and sits back down — and the two silent failures it cost: a walk target that defaulted to the middle of the map, and a graph edit that compiled perfectly into a chain nothing ever executed.
-
Twelve bus stops, and seven of them landed on the empty ring road
Putting a timetabled bus on a real route through the estate — how the stop siting quietly collapsed, why the driver ended up crumpled on the cab floor, and what is still untested.
-
The editor had to be shut down before the optimisation would run at all
An open-world map with effectively no level-of-detail data anywhere took the graphics card down twice while trying to fix itself, and the answer was to stop the editor drawing and do the work in three separate headless processes.
-
The coin pile never settled, and the frame rate was the reason
Building a working penny pusher out of several hundred real rigid bodies, and the feedback loop where slow frames stop a pile settling, which keeps the bodies awake, which keeps the frames slow.
-
The dialogue panel validated clean, reported ten widgets created, and rendered a blank white rectangle
How this game's conversation UI stopped being one hand-drawn panel copied forward by duplication, and the class of silent failure that arrives the moment an agent can author widget trees for you.
-
A scratchcard you hold in your hand, and the two ways it went invisible
Rebuilding a full-screen scratchcard widget into a card held in the world, how the wax removal actually works, and why the card rendered pure black while the coin on top of it looked perfect.
-
Proving a physics roulette wheel is fair, and the two tests that lied about it
The betting shop's roulette wheel is a real rigid body in a real bowl, so the winning number is wherever it stops - which means fairness has to be measured rather than asserted, and the measuring is where all the interesting failures were.
-
Eleven in the morning rendered like dusk — the camera was cancelling out the difference between day and night
The daytime street looked identical to the night street, and it was not a grading problem — the sun was set to ten lux against a real daylight figure near a hundred thousand, and with no outdoor exposure authority the automatic metering re-normalised both to the same mid grey.
-
Everything I could not automate turned out to be a missing server
Adding a second agent server to the same live Unreal editor retired four "the human must do this by hand" rules overnight, and the real win was the observation loop rather than raw speed.
-
A dancer on the beat, because the beat is a number and not a signal
The nightclub got a music-reactive light rig and one dancer who moves in time with the track, and the reason it works is that tempo is measured offline and baked while only loudness is read at runtime.
-
I kept paying for the same silent failure twice, so I wrote the traps down
A project-resident skill file of verified recipes and silent-failure traps, indexed by symptom rather than by subsystem — why writing each trap down as you pay for it compounds, and where the practice still falls short.