Find the playable promise first.
The project began as a compact test around train pressure, delivery goals and first-person resource management.
Case study
Completed playable Unreal Engine demo about running a corporate train through a frozen world of debt, quotas and scarce resources.
Overview
Cold Engine started as a short capability check and grew into a complete demo. The project tested whether a small team could build, present and release a playable first-person survival-management experience in Unreal Engine.
The player manages a train in an industrial frozen world, balancing deliveries, energy, temperature, cargo pressure and corporate quotas while moving between stations.
Production story
The roadmap keeps the process visual: each step has a concrete media frame and a clear production decision.
The project began as a compact test around train pressure, delivery goals and first-person resource management.
Contract choice, route danger and delivery stakes were shaped into a short loop a player can understand quickly.
The cabin, cargo and train state became the player-facing layer for energy, resources and cold-world survival.
The movement setup was reworked so the team could finish the demo instead of repeatedly fighting scene cost.
Materials, props, snow mood, CRT-style interface pieces and video capture were brought together for public presentation.
The work ended as a complete Steam-facing demo with systems, visuals, audio, presentation material and a clear role split.
Main challenge
The original setup kept the train and player static while the world simulated movement, making the scene heavy and hard to scale.
The movement approach was reworked so the team could stop fighting the same performance blocker.
The main bottleneck was removed, making the demo stable enough to finish and present publicly.
Project takeaways
A quieter summary of what the project says through the work itself.
A playable demo was scoped, assembled, presented and pushed to public-facing release material.
The project stayed centered on one readable loop instead of expanding beyond what the team could finish.
The optimization issue was treated as an architecture problem, not just a polish task.
The page separates my design, art and production ownership from programming and audio collaboration.
Next step
I can walk through the build, media, role split and production decisions in a focused conversation.
Related work
Route choice, contracts and train state readability for the survival loop.
Cabin, cargo, station and industrial props tied to gameplay clarity.
Atmosphere work that supports mood and player readability.