Research Focus
For Voyage, I researched hard-surface modelling as a production method for building believable sci-fi assets. This was important because the film included multiple mechanical and manufactured objects: the robot companion, spaceship, sci-fi pistol, pendant and environment props.
My aim was not only to model visually detailed assets, but to create assets that were readable, efficient and suitable for a realtime Unreal Engine pipeline.
Industry Context
Hard-surface modelling is commonly used for mechanical objects, vehicles, weapons, props and architectural forms. Unlike organic modelling, it depends on clear geometry, controlled edges and precise surface transitions. Industry discussions often emphasise that good topology is not about making every surface perfectly quad-based, but about whether the model serves its production purpose: clean shading, stable baking, readable silhouette and efficient performance.
Polycount’s topology resources define topology as the arrangement of vertices and edges across a mesh, and connect good topology with realtime performance. This was relevant to my project because Unreal Engine assets need to look strong in camera while remaining technically stable.
I also researched face-weighted normals and bevel workflows. Polycount describes face-weighted normals as a method for improving hard-surface shading by combining bevels with adjusted vertex normals. This influenced my modelling approach because many sci-fi assets need crisp edges, but completely sharp edges can look unrealistic under cinematic lighting.
Application to Voyage
In the film, I used hard-surface modelling to support both world-building and production efficiency.
The robot companion required a balance between mechanical construction and emotional appeal. Its body needed to feel engineered, but its proportions and face screen had to remain cute and readable. Therefore, I focused on simple large shapes first, then added smaller mechanical details only where they supported the design.
The sci-fi pistol and spaceship used a more industrial design language. For these assets, I focused on silhouette, panel separation, bevel consistency, and functional details such as handles, vents, bolts, seams and material breaks.
The pendant was smaller, so the design needed stronger shape readability. At small scale, excessive detail can become visual noise, so I prioritised clear forms and controlled surface detail.
Production Workflow
My asset workflow followed this structure:
- Blockout — establish silhouette, proportion and function.
- Hard-surface modelling — refine panels, bevels and mechanical forms.
- Detail pass — add seams, vents, bolts, decals and secondary shapes.
- UV preparation — organise texture space and maintain consistent texel density.
- PBR texturing — create material separation through roughness, metallic values and edge wear.
- Unreal Engine testing — check lighting response, scale, readability and render stability.
This process helped me avoid treating modelling as an isolated task. Each asset had to work inside the wider cinematic system: lighting, materials, camera distance and realtime performance.
Realtime Considerations
Because Voyage was produced in Unreal Engine, I also researched realtime asset optimisation. Unreal Engine’s Nanite documentation describes Nanite as a virtualised geometry system designed to render high detail and high object counts by processing visible detail efficiently.
However, this research also reminded me that optimisation is not only about using one technology. For a student film, I still needed to make careful decisions about mesh density, material count, texture size and scene organisation. Hero assets could hold more detail, while background props needed simpler geometry and stronger silhouettes.
This helped me separate assets into production categories:
- Hero assets: girl character, robot, spaceship, pistol
- Secondary assets: pendant, equipment, smaller props
- Background assets: environment set dressing and repeated details
This hierarchy helped me spend time where the camera would actually notice it.
Reflection
This research changed how I approached hard-surface modelling. I learned that a successful asset is not simply a detailed model. It must have clear design logic, clean shading, efficient structure and a purpose inside the film.
The most important lesson was that modelling decisions affect every later stage: UVs, baking, texturing, rigging, lighting and rendering. A poorly planned model can create problems throughout the pipeline, while a clean asset supports smoother production.
For future projects, I want to improve my modular asset workflow further. I would like to build reusable sci-fi parts, shared trim sheets and stronger asset libraries so that production can become faster and more consistent.
Research Links
Polycount — Topology
https://wiki.polycount.com/wiki/Topology
Polycount — Face Weighted Normals
https://wiki.polycount.com/wiki/Face_weighted_normals
Polycount Forum — Topology Standards for Hard Surface Modeling
https://polycount.com/discussion/208575/topology-standards-for-hard-surface-modeling
80 Level — Hard-Surface Modelling and Lighting in UE4
https://80.lv/articles/high-voltage-hard-surface-modeling-and-lighting-in-ue4
Unreal Engine — Nanite Virtualized Geometry
https://dev.epicgames.com/documentation/unreal-engine/nanite-virtualized-geometry-in-unreal-engine
Polycount Forum — Game-Ready Asset Modelling Workflows
https://polycount.com/discussion/234552/questions-about-game-ready-asset-modeling-workflows

