3ds Max: Working with big scenes

Ravelin3D 2015-02-17 09:42 tutorial  > 3ds MAX  > misc

A tutorial by Ravelin3D studio.

"How to make up a tremendous master plan better"
How we do it in Ravelin3D studio (tips and principles).

Click on image to enlarge nr_pushkin1_947.jpg

Large scene

 

Click on image to enlarge nr_pushkin2_948.jpg

Large scene

 

Click on image to enlarge nr_pushkin6_951.jpg

Large scene

Introduction

Based on the statistics on our site the visualization we make is more often designed for big residential complexes and villa communities. Sometimes these projects consist of dozens of multistory blocks, and the 3D-scenes include great number of greenery, automobiles, people and other objects of fillings. Most of all, our clients don’t have the ultimate version of materials and that is why we have to make such-like projects upon the conditions of numerous corrections and alterations. We prefer to work in 3D and avoid compositing in 2d software, as it is easier to correct something in 3D, than constantly make changes in post-production.

The most frequent question we’re asked: "How do you render such tremendous scenes? How your 3D Max manages with it? Perhaps, you have really cool hardware".

The answer is: No, the hardware we have is common as dirt. However, we work taking into account two important principles:

  • We do not work on anything that cannot be seen by camera in the scene
  • We organize our projects and workflow.

After reading this article, it can seem to you that these rules just slow down the work. However, this assumption is deceptive. These principles rapidly fall into habit, and the only thing you need is to constantly follow them. As a result you will be able to work with scene of any volume in the shortest terms.

Click on image to enlarge nr_pushkin7_952.jpg

Large scene

 

Click on image to enlarge nr_pushkin8_953.jpg

Large scene

 

Hardware configuration

Let us start with typical configuration of computers that are used in Ravelin3D studio.

  • Intel i7 3770k
  • 32 GB RAM
  • SSD drive
  • Graphics card: GTX 650 2 GB
  • x64 Windows, with possibility of passing over the restriction of 3 GB of possible physical memory.

As you can see, our computers are rather powerful, but not uncommon (quite up-to-date setup for 2015). The secret of success is scene organization and workflow.

Control polycount

nr_polycount_946.jpg

The number of polygons the main scene rarely exceeds 16 millions.

  • We don't model minor details, we don't bevel objects that will be placed far from camera.
  • On the average, we put more than 200 thousand of polygons per a high-rise apartment building.
  • We use "Turbosmooth" or "MeshSmooth" smoothing only when it is really necessary.
  • If an object is smaller than 20 cm and it is not in front of camera, we do not model it.

If you want to sort quickly objects by polycount, add the "Faces" column to "Select by name" menu and sort all the objects by quantity of polygons.

nr_faces_942.jpg

Use VrayProxy

We use "VrayProxy" for all objects with a lot polygons. This is very important, especially regarding trees, bushes and automobiles, as they consist of many polygons and, as a rule, we often copy them into scene. We convert objects into "VrayProxy" before importing them to scene. It is not worth the trouble to make conversion into "VrayProxy" in the main scene, it can lead to errors. After "VrayProxy" objects are put in scene, turn on the "Bounding Box" display mode, it will reduce the load on graphics card. It is especially relevant if the scene contains many "VrayProxy" objects.

nr_bounding_box_0937.jpg

Tip: The copy of “Instance” of each unique “VrayProxy” (for example, each unique tree) can be removed from working area and put in one place. Border this area with a rectangle - in such a way you won’t miss small “VrayProxy” colours or small bushes. This set can be easily exported to other scenes. Use this approach and you’ll have ready-made sets of “VrayProxy” frequently used objects at hand. You will not have to make them from scratch.

Instancing and scattering

If you need to copy objects, that will not be edited later, use copy as “Instance”. If there are more than 20 objects, use “MultiScatter”, especially when copying repeating objects (mostly greenery). Make “MultiScatter” presets for copying elements in advance.

Click on image to enlarge nr_controllers1_938.jpg

The scene is on the left, grouped proxy and scattered sets of objects are on the right.

 

Click on image to enlarge nr_pushkin3_949.jpg

Large scene

 

Use Xref - You can find it under File > References > Xref scene

We use “Xref” to optimize workflow. It’s especially important, when several specialists work on the same project. With “Xref” you can build a scene from several parts. Each co-worker can work on his part independent of the rest of the team. Main scene will be constantly updated during this process.

 nr_folders_943.jpg

Example: the project main scene is scene.max, which includes master plan, greenery, cars, and other objects. Houses for this project are in separate scenes “house1.max”, “house2.max”, etc.
Buildings “house1” and “house2” are uploaded in “scene.max” from individual files. They cannot be edited in “scene.max”, but they are rendered along with it. Quick and handy.

Click on image to enlarge nr_xref1_964.jpg

Xref files are helpful during teamwork

 

 nr_xref_off_963.jpg

If necessary, you can turn off displaying these houses in viewport — it significantly saves resources.

Use Layers

We actively use layers for the purpose of convenience and work optimization.

Click on image to enlarge nr_Layers_944.jpg

Layers allow us to turn off a group of objects which is unnecessary at the moment.

 

Optimize materials and viewport

We use only JPEG textures. We recommend not using TIFF and PNG textures, since they consume a lot of memory and significantly slacken overall performance.

Use only “Vray” plugin materials. If there’s imported model with standard materials – pass it through “Vray mtl converter” plugin. It automatically converts all materials to “Vray” format and prevents all possible errors and drawbacks of displaying. We recommend checking big scenes with this plugin from time to time. Standard materials can be a cause of shut-downs when rendering. Use one copy of one material in a scene. Do not copy it unless necessary. For example, if one material is a part of “MultiSub”, than copy it there, using “Instance” copying. Optimize the number of “subdivs” parameter in materials. Do not overrate them unless necessary, the standard amount of “subdivs” – “8-20”. Sometimes in reflecting objects with the use of “glossy” parameter, the number of “subdivs” should be increased. For example, to “30” in order to avoid noise.

Optimized viewport is a formula for quick and effective work. For the sake of convenience when working with large scenes in viewport, we follow these rules:

  • Use “Nitrous” mode in viewport when assembling scene.
  • Hide textures, if you are not working with UVW Map. All textures can be hidden in Display > Shaded: object Color.

nr_shaded_961.jpg

To increase viewport performance you can put multipolygonal objects in “Box” display mode.

nr_display_as_box_941.jpg

 

Click on image to enlarge nr_controllers2_939.jpg

All “VrayProxy” и “MultiScatter” objects are taken out of the working area in scene and are signed.

 

All “VrayProxy” objects, which aren’t worked at, are displayed as “Box”. Set all “MultiScatter” objects with ready settings to minimum values in “Preview” parameter, “Preview type: Box”.

nr_multiscatter_box_945.jpg


Use “Adaptive Degradation” mode in viewport settings.

nr_degradation_940.jpg
Color your groups. For example, all trees can be coloured with one colour using “Object color” parameter. In such a way it will be easier to understand the scene, and you’ll get handy masks as a bonus when rendering.

Use “Viewport clipping” when modeling.

Render regions

We actively use “Region render” computation method to change a scene and render the only changed area. If we change something and want to do a quick preview, we hide all “multiscatter” and “proxy” objects that are not used at the moment. This way we save memory and rendering is greatly accelerated.

Prepare scene to rendering

In our studio all images are rendered by means of “distributive render” on several computers. To avoid problems regarding parallel rendering follow the next rules:

  • There should be no lost textures. Lost textures path can be restored using “AssetTracking” (Shift+T), if textures are impossible to find, replace them with grey “pads” with the same name and file extension.

    Tip: when importing or merging a model from libraries to work scene, check and optimize it in a separate clean scene. It helps to avoid problem materials, lost textures and other troubles.

  • Scene should not contain Cyrillic characters or any other languages characters in names of objects, materials, scenes, etc. Only Latin characters. Network render doesn’t support Cyrillic characters, it’ll lead to errors when rendering.
  • Scene should not include standard and Raytrace materials. It causes scene hanging up, shut-downs or spots.

    Tip: before rendering use Vray standard converter of materials— right click in scene, “convert all materials to vray”.

 nr_vrat_convert_962.jpg

We use rendering across a network, that’s why all work files should be on server. We don’t store files on local computers since in this case there will be places without textures in render or lost proxy.

Render standard settings:

Click on image to enlarge render_settings_4.jpg

Vray Global switches:

Reflection/refraction max depth: 3 — this parameter is enough for most of scenes. Unnecessary rereflections are not rendered. It can be increased when necessary.

Vray: System
Default geometry: Static
Dynamic memory limit: 30000 MB
It significantly speeds up rendering.

I hope my tips will help you when working with very large projects.
Follow us on our Behance account: https://www.behance.net/ravelin
Good luck!

Click on image to enlarge nr_pushkin10_954.jpg

Final image after post production
Author: Ravelin3D Editor: Michał Franczak
Tags: scene proxy large tip huge ravelin3d
You may also like...
Tip of the Week. Exploring ForestPack4

Tip of the Week. Exploring ForestPack4

Forest Pack is a plugin for Autodesk 3ds Max, and 3ds Max Design, designed to give a complete solution for creation of vast surfaces of trees and plants.
×

LEAVE A COMMENT

You need to be logged in to leave a comment. Don't have account? Register now.
Piash16:14:40  |  17-02-2015
Thanks a lot for the tips ... very helpful
ak_ind12:49:39  |  19-02-2015
gud tips ..thanks alot
zonademagia14:55:09  |  23-02-2015
Great tutorial! Thanks! :)
gaynm17:29:45  |  03-03-2015
dude this is very helpful
Munkhuunuu07:50:18  |  04-03-2015
THANKS
GeorgeJ14:38:47  |  06-03-2015
Beautiful job! Does anyone know of a tutorial on texturing the roads like this? Thanks.
Deaff12:09:19  |  10-03-2015
to GeorgeJ14 To create huge master plans, and filling their texturing, I will write a separate lesson. Soon :)
suresh_s_s08:02:14  |  20-03-2015
good tips
Redsteel09:15:47  |  08-06-2015
Thank you very much for the tips and tutorial
panda7210:22:26  |  11-03-2016
your tips are very usefull, I use some of them, but not all and i have many problems in viewport. I wonder if you are still planning about the tutorial about how to create huge master plans, and filling their texturing. My big problem is the area around my workplan, i've always to use photo or google, and the result is not so beautifull as a modelled background... like a VUE background. your road are so beatifull too... bye, Luca
nonamesmallkid16:46:41  |  24-03-2017
How to solve the warning : Scene bounding box is too large.

+ ADD A COMMENT

  • ul. Przedzalniana 8, 15-688 Bialystok, POLAND