How do you organize 3ds Max/Corona project folders, render outputs, and revisions?

V-Ray V-Ray Common Public
, , , ,
1

I’m an archviz visualizer working mainly with 3ds Max and Corona, and I’m trying to improve how I organize projects in real production.

Once a project grows, things can get messy quite fast:

  • Multiple spaces or rooms
  • Multiple cameras
  • Test renders
  • Final renders
  • Client revisions
  • Assets and texture folders
  • Backups
  • Final delivery folders

The actual rendering part is one side of the job, but keeping everything clean, traceable, and easy to find becomes another challenge by itself.

I wanted to ask how other Corona users handle this:

  • Do you follow a fixed folder structure?
  • Do you keep camera-wise render folders?
  • How do you separate test renders, finals, and client revisions?
  • Do you use any scripts/tools, or is it mostly manual discipline?
  • What part of this workflow usually becomes messy for you?

I’m mostly interested in real archviz workflows for interiors, villas, apartments, hospitality, and multi-space projects.

Curious how others handle this in production.

Thanks.

2

In most places I worked it usually comes down to ‘a fixed folder structure’. It usually works well and is easy to follow for every single job regardless of size.

Here is an example of the structure I find works best for me:
00_Internal
01_Information
02_3D
03_Outputs
04_Proofs
05_Post_Production
06_Final_Images

All information that is requested to the client goes in Internal - eg. Can you clarify this DWG. All that will go in a dated folder such as:
00_Internal
– 20260713_DWG_Clarification

This works the same for 01_Information (received information from the client).

02_3D is where all the 3D files go. They usually have a SKU, description and internal/external versions eg:
CKPU_Facades_v0101.max
CKPU_Living_v0101.max

Sometimes you can keep everything in one max file for the Living, Kitchen, etc but sometimes you need to split them off into their own file, what matters here is the description that matches the output. So if that happens keep things simple for yourself like:
CKPU_House1_Living_v0101.max
CKPU_House1_Kitchen_v0101.max

03_Outputs - all renders go here, including tests, they should be versioned with internal/external, this means your first version number can be anything but lets you know how many times the client actually received it as per the second number eg:
CKPU_House1_Kitchen_v0101
CKPU_House1_Kitchen_v0201
CKPU_House1_Kitchen_v0301

3 Internal tests/revisions, client will receive first time (xx01). Once the client has seen it the external version (2nd number) increments to xx02 eg:
CKPU_House1_Kitchen_v0402

04_Proofs - This is what is actually sent to the client, low or half resolution. Usually the Jpeg. Name should match the last output including version numbers.
05_Post_Production - Same naming structure as the 3D/Output folders.
06_Final_Images - Same naming structure but these are the highres images for delivery.

In regards to your question about scripts/tools, yes lots of them. If something can be automated, it should be. This helps reduce technical/cognitive load.

Regarding your question: What part of this workflow usually becomes messy for you:
Following this structure usually not much other than not being descriptive enough with your filenames. However since the Proof folder usually shows exactly what was delivered to the client its a quick way to flick through the renders, check what renders match to the 3D files (since they are named the same) and get back on track relatively fast. This method also applies to the Outputs and Post Production files.

If you have multiple cameras then be more descriptive eg:
CKPU_House1_Kitchen_Camera1_v0101

As for assets/textures, these are referenced from the asset library, on a NAS.

Once a project is ‘complete’, the project is archived with all the assets for that job and moved to a different location. These projects are mirrored to another drive and taken off site for flood/fire safety.

Hope that helps in some way