ENV Perimeter | #05 From Shots to Production

Turning Decisions into Production

In the previous update, I narrowed the scope of the project to four key shots. Selecting the shots was only the beginning. Now every production decision had to support those images. Instead of treating the environment as one large project, I started breaking it down into individual production tasks.

Breaking the Environment Down

The first step was identifying every asset visible in the selected shots. Each object received a unique production ID that also became part of its naming convention in Unreal Engine. This made it easy to locate assets in the scene, track their progress and keep the project organized as it continued to grow. The goal wasn't simply to organize the environment. It was to understand:

• what had to be built,
• what could be reused,
• what could be instanced,
• what depended on other assets,
• and what would have the biggest impact on the final presentation.

Unlike my previous production work, where large parts of a scene could be assembled from existing asset libraries, every new asset in this project became a production decision. Replacing or redesigning an asset later in development doesn't just affect the scene it can impact materials, composition, dependencies and production time. That made planning just as important as modeling.

Production Priorities

Once every asset had been identified, I built a production tracker. Not as a checklist.  As a decision-making tool. For every asset I track:

• production stage,
• priority,
• instancing,
• production status,
• dependencies,
• notes.

The tracker isn't there to tell me what is finished. It tells me what deserves my attention next.

Working Smarter

By this stage, most of the environment already existed as a blockout. The challenge was no longer deciding what needed to be built, but in what order. Every asset would eventually need to be completed, but the selected shots helped determine which ones would bring the greatest value to the portfolio first. From that point on, I evaluated every task based on its contribution to storytelling, its visibility across multiple shots and its impact on future refinements. This production order wasn't fixed it became a framework for continuously re-evaluating the project. As each asset was completed, it became easier to decide whether another element still added value, needed refinement or could be removed altogether. Instead of asking, "What should I model next?", I started asking, "What will have the greatest impact on the final presentation?"

Two Sources of Truth

Over the years, I've worked with different planning tools, including Miro, Ftrack and Figma. all are excellent for brainstorming and organizing ideas, but for a project that evolves every day I needed something much easier to sort, filter and update and copy data from. In the end, I chose a simple spreadsheet. Sometimes the simplest tools are the most effective. The spreadsheet became the production tracker, while PureRef evolved into a visual map of the project.

Each selected shot was annotated with production IDs, allowing me to identify every visible asset and connect it directly to the production tracker and its naming convention in Unreal Engine. I now treat both documents as living parts of the project. They continue to evolve alongside the environment, helping me identify missing assets, reorganize priorities and integrate new ideas into the production pipeline without losing track of what has already been planned.

ENV Perimeter | #04 Choosing What Matters

Changing the Goal

After changing the way I looked at the project, the next challenge became surprisingly simple.

What should actually stay?

For years I had been building complete productions, where every part of the project contributed to the final result. Portfolio work follows a different set of rules. That completely changed how I evaluated every new idea, every new asset and every hour invested in production. Every decision was measured against one question:

Would it make the final presentation stronger?

A Different Measure of Success

One of the most valuable lessons I learned was that a broad project scope still has value. It demonstrates that you're capable of handling larger productions, and that's certainly valuable. But that's only part of the picture. At first, I wasn't completely convinced. Years of approaching projects from the top down were difficult to set aside. As I studied portfolio examples together with the reasoning behind them, that idea gradually started to resonate with me.

I realized that a broad scope shows you're capable of building an entire world. A carefully chosen fragment shows that you know how to deliver quality where it matters most. Looking back, I think both ways of thinking are equally important. Designing from the top down helps you understand the project as a whole. Designing from the final shots back toward the environment changes the decisions you make along the way.

Being able to move between those two perspectives has probably been one of the most valuable lessons of this project.

Choosing What Matters

Reducing the scope didn't mean reducing the ambition. It meant becoming more selective. Entire sections of the environment stopped being priorities because they didn't strengthen the final presentation. Every asset had to justify both the production time invested in it and the value it added to the final shots. Instead of trying to finish an entire military base, I focused on creating a small number of carefully planned portfolio shots.

The project is currently built around four key shots. Each one has a different purpose while contributing to the same story.

• Wide establishing shot
  Showing the entire warehouse. A fallen tree has collapsed part of the roof, drawing attention to the activity still happening inside.
  
  
• Medium shot
  Focused on the repair station, showing the relationship between the two APCs. The goal is to make it clear that, despite the damage, the
  warehouse is still functioning as a military repair facility.
  
  
• Close-up
  Inside the repair area, focusing on the APC, interior lighting, tools and mechanical details to create a more intimate, story-driven moment.
  
  
• Road approach shot
  Viewed from the access road to establish the overall context of the environment.

Looking Back

Limiting the number of shots wasn't about making the project smaller. It was about making every decision more intentional. Ironically, by deciding to show less, I found a much better way to show what I can actually do.

ENV Perimeter | #03 Experience Isn't a Portfolio

Challenge

One of the biggest challenges during this project wasn't modeling, texturing or learning Unreal Engine.

It was understanding how to present more than twenty years of professional experience in a way that actually speaks to the game industry.

As the project continued to grow, I started questioning whether I was investing my time in the right places. Throughout my career, I had always worked on complete productions rather than isolated portfolio pieces. Naturally, I approached this project the same way, expanding the entire environment instead of focusing on the part that would best represent my skills..

The project kept getting bigger because that's how I had learned to build environments throughout my career. Building only a small part of the world felt incomplete, even though that was exactly what a portfolio piece needed.

I reached out to several experienced artists and received a lot of valuable feedback. While those conversations helped, most of the advice was naturally quite general and didn't answer the problem I was really trying to solve.

For years, building the entire environment had simply been my way of working. I had to learn that a portfolio piece doesn't need to show the whole world. It only needs to show the part that tells the story.

The Right Perspective

The turning point came when I finally received feedback supported by real portfolio examples. Instead of discussing individual assets or technical details, we focused on what actually makes an environment piece hireable.

I'm genuinely grateful for that guidance. It completely changed the way I looked at the project.

For the first time, I stopped evaluating the environment as a complete production and started evaluating it as a portfolio piece.

I stopped asking: "What else can I build?"

and started asking: "What will make this portfolio stronger?"

Looking back, I also realized that despite many years of professional experience, I had neglected one important part of my career: my portfolio.

Like many artists working in production, I spent most of my time focused on client work, deadlines and delivering commercial projects. Personal work was always something I planned to do later.

When you're fully committed to production, it's surprisingly easy to stop documenting your own growth.

Only when I decided to transition into game development did I fully understand the cost of that decision.

Late-night personal projects became the bridge between my production experience and the portfolio I needed, but they could never replace years of consistently documenting my work.

Looking back, if I had invested even a small amount of time updating my portfolio throughout my career, this transition would probably have been much smoother.

Story First

Once I stopped thinking about building a bigger environment, I could finally focus on what I actually wanted the project to communicate. Then I realized something even more important. I wasn't reducing the project. I was removing everything that distracted from what I wanted to communicate. That realization went far beyond portfolio building. This project reminded me why I chose art in the first place. Long before I worked professionally in 3D, I spent years drawing, painting and sculpting. Back then, the medium was never the goal. It was simply a way of expressing an idea. Today, Unreal Engine, Blender and every asset I create serve exactly the same purpose. The tools have changed. The purpose hasn't.

Final Thoughts

Professional experience builds your skills. A portfolio makes those skills visible.
Purpose gives them meaning.

That's when I realized I didn't need to build a bigger world. I only needed to build the part that was worth telling.

ENV Perimeter | Behind the Design #02

From Arch-Vis to Gamedev

One of the biggest challenges during this project wasn't modeling. It was changing the way I approached environment creation.

In architectural visualization I was used to working with mature asset libraries that had been developed over many years. That allowed me to focus on composition and storytelling while creating only the assets that were truly unique and couldn't be sourced from existing libraries. This project forced me to rethink that workflow.

Every asset is created from scratch, so every new model has to justify both the production time invested in it and the value it adds to the project. Instead of simply expanding the environment, I started asking a different question: Can this asset support the story while also becoming part of a reusable production library? 

The Birch

The same challenge extended to vegetation. Since it plays a major role in this environment, I decided to build my own procedural tree generation tools. Although that work was valuable, it also shifted the project's focus toward tool development instead of the environment itself. It became another reminder that every technical decision comes with its own production cost.

The Shelter

The Shelter was originally intended to be the main focal point. The idea was to create a strong contrast between a massive reinforced military structure and the surrounding forest, while the warehouse played only a supporting role.

The Warehouse

As production progressed, however, I realized the warehouse offered far greater opportunities for both storytelling and reusable assets. It naturally evolved into the project's primary location. Originally, the warehouse served as the logistics and maintenance hub supporting the nearby shelter. After being partially destroyed during the conflict, it was repurposed as a temporary APC repair depot.

That narrative also justified a much broader range of reusable assets. APC components, maintenance equipment and workshop props all became part of the same production library, reducing the number of unique models while making the environment feel more believable and functionally consistent.

A Turning Point

ENV Perimeter |  #01 Project Vision & Goals

ENV Perimeter is a long-term Unreal Engine 5 environment project focused on building a believable military logistics facility while developing production-ready environment and hard-surface workflows.

The project combines environment art, realistic military infrastructure, reusable hard-surface assets and environmental storytelling within a realtime production pipeline.

While modern AAA production relies heavily on reusable asset libraries, outsourcing and shared production pipelines, I'm intentionally creating every asset myself.

This is a conscious decision. The objective isn't to learn how to model, but to understand the trade-offs behind production decisions. By experiencing every stage of the pipeline firsthand, I can better evaluate when an asset should be unique, when it should become reusable, how it affects optimization, and where production time creates the greatest value.

Each development stage will be documented, from planning and modular asset creation to environment assembly, storytelling and final presentation.