#workflowinspiration

Using a Night Scene Breakdown as a Presentation Workflow Reference

For this part of the pre-production document, I wanted to include a workflow reference that was less about environment type and more about presentation discipline. Stephen Falk’s UNSC Outpost breakdown was useful because it treats composition and lighting as decisions that need to be planned early, not just polished at the end. What mattered to me was not the fact that it is a night scene, but the way the project is built around thumbnails, focal hierarchy, value control, and purpose-driven design. That makes it surprisingly relevant to EREMUS, even though my own environment is a desert outpost rather than a Halo-inspired forest scene.

Final Beauty Shot of the Outpost Final scene image used as the main benchmark for how lighting, focal hierarchy, and composition are resolved in the finished environment.

Thumbnail / Planning Sketches Early planning sketches from the article, used to show how composition was explored through thumbnails before detailed production. Falk explains that he made rough thumbnails and landscape sketches to establish composition before moving forward.

Blockout / Building Design Image Reference used to study how the structure becomes stronger once its purpose is clearly defined. In the article, Falk says that once he decided the base was a temporary battlefield outpost, the functional details became much easier to design.

Annotated Composition / Lighting Useful example of how focal point, leading lines, and lighting work together to guide the eye through the scene. Falk explicitly frames lighting around focal point, contrast, full value range, palette, movement, and rule of thirds.

What I Took from This Workflow

The biggest takeaway for me was composition first. Falk explains that one of the weaknesses in an earlier project was the lack of contrast, strong focal point, leading lines, sense of scale, and physically correct lighting, so this time he spent much more time planning composition through thumbnails before production began. That feels very relevant to EREMUS, because I also want to make sure the outpost reads clearly inside a larger landscape rather than relying on detail alone.

The second lesson was purpose-driven detail. In the modelling section, Falk says he had been guilty in the past of filling a blockout with meaningless detail, so here he defined the actual function of the building first. That approach is useful for me because EREMUS also needs to feel like a believable survey-relay outpost, where forms, props, and extensions are connected to use rather than decoration.

The final lesson was lighting as composition control. Falk describes lighting as one of the most pivotal parts of environment art and says he kept in mind focal point, contrast, full value range, palette, movement, and the rule of thirds while building the scene. He also explains how color contrast was used deliberately, keeping most of the scene in muted blues while reserving orange for the garage focal point. Even though my project uses desert sunlight instead of moonlight, that way of thinking about exposure and visual hierarchy is directly useful for how I want to present EREMUS

Reflection

Using Grand Space Opera as a Workflow Reference

At this stage of the pre-production document, I wanted to include at least one environment breakdown that was useful not just visually, but structurally. Grand Space Opera stood out because it presents the environment as a clear production process rather than only a final beauty render. What I found most useful was the way the project is broken into landscape generation, nature, and man-made objects, which feels very close to how I want to structure EREMUS: terrain systems first, optional biome support second, and hard-surface outpost assets as the main built layer.

Final Beauty Shot from Grand Space Opera Final environment image used as the overall workflow benchmark for quality and structure.

Blockout Screenshot Blockout reference showing how composition, focus points, and scene planning were established early.

Houdini Terrain/HDA Overview Terrain workflow reference used to study how the environment is treated as a controllable system rather than a single sculpt

Landscape Layers / Generation Breakdown Supporting reference used to understand how the environment is built in separate production layers.

What I Understand from This Workflow

The strongest lesson for me was the importance of starting with blockout. In the article, Karabardin explains that blockout was used to determine foreground, background, focus points, guiding lines, and an early pass for lighting before the scene moved into detailed production. That was useful for EREMUS because it reinforced the idea that I should lock the scene boundary and composition before committing too heavily to assets or procedural tools

The second lesson was how the terrain is treated as a system. The article explains that the landscape was built in Houdini through two HDAs, with structured inputs such as terrain, preserved area, cliffs, rivers, and lakes, before being brought into Unreal as a layered landscape. That is very close to the kind of thinking I want in EREMUS, where the terrain should be controllable and iterative rather than just a sculpted backdrop.

The final takeaway was the layered production logic. The scene was not built as one giant pass. Instead, landscape, foliage, and hard-surface content were developed as separate but connected stages. Even though EREMUS will be much less foliage-heavy, that breakdown still feels useful because it gives me a cleaner way to organise the project into terrain, optional biome, and outpost systems.

Reflection