The Orchestrator runs through your scene and identifies proxy objects/converts them to an editable polygon. However, most of the time these proxy objects are heavy and there is a reason why they needed to be proxies in the first place, so the process will automatically optimize the object down to an acceptable size (typically it will apply a Pro-Optimizer of 25%). The reason for this is to tackle large vegetation areas which typically will use Proxies/scatters although this can sometimes affect the final result of the object especially when you have a bed that has smooth/clean topology.

When it comes to vegetation, I would leave the proxies how it is since the Orchestrator will try to handle this. On the other hand with furniture/decor items, I would suggest converting the proxy objects to an editable mesh (depending on what renderer you use) then possibly breaking up the object by materials since the orchestrator does a "Pre" optimize step which flags any objects over 1 million triangles and reduces it down to an appropriate size - this means that it will only optimize in the final step once it's baked and maintain it's texture quality.

Sometimes the back face of a mesh will penetrate through the mesh and will stop light from hitting the correct side of the object.

Example:

Sometimes it is optimization BEFORE you bake that causes this face intersection. Therefore, if you bake before optimizing the light will be baked correctly and the intersecting faces that are caused by optimizing will not be able to cast shadows.

You can resolve this my moving/deleting the geometry that intersects with the correct facing part of the model. Since it won't be seen anyway this should resolve the issue.

This is common with curtains and plants. This issue can be resolved in the Space Editor when you are editing your reflections.

Check your material doesn't have a high blur level applied as this will blur the texture.

Assuming you are not already over your texture usage budget, you can simply bump your map up once stage in the Master Layers tab and most of the time this will resolve a noisy texture.

It is important to make sure you're baking for minimum of 30 minutes to achieve a clean texture

If you have a layer, say a ground and it is very large 4K may not be enough. You could break it up into multiple objects in different layers and bake x2 4K's instead. Just be aware that every 4K takes up 2% of the total scene budget so you may instead want to reduce the size of the plane if it isn't critical to the model

We automatically select resolution based on surface area. But each layer will fall into a different bracket depending on their surface area.

These are the brackets:

Because these are brackets, experiment with lowering the quality of some layers and re-baking as you may believe the quality difference is negligible depending on the layer.

Unless modeled intentionally, it is likely that your model contains geometry that the user will never see if you did not use the Pre-Deleter in the Orchestrator. If you delete faces that can't be seen that will leave more texture space for the rest of the layer. It's particularly good to be thinking about large flat areas that are not visible to someone exploring the space; e.g. the insides of walls, the underside of a roof, the bottom of a large ground plane around the model.

If you look at the baked PNG's in the Bake folder next to your max file you can identify layers with lots of non-visible wasted texture space by looking for things that are entirely black/unlit (see example below).

Potential reasons:

Note: When your Baking (rendering) is complete, you will have multiple images located in your “Bake” folder (you can view these image at any time to adjust/edit and check for issues). Currently the baking feature does not support Displacement or Fall-off maps and the displacement option will produce a black map if it is not turned off in the Render settings, however it is automatically turned off as part of the EnvizPro Process. Rarely does the unwrapping process make mistakes but you can make edits to the UV map located as the highest channel if you need to.

Solutions:

If you have maps that obviously don’t look correct, then the first point of action will be to check the UV channel 8 for overlapping UVs. These are colliding UV islands that can create fractured images and are obvious to identify.

Next you can double check the displacement is turn off in the Render Settings > Common tab.

Lighting can always be a factor that can affect the final output i.e.: missing or turned off lights. You should always double checking your lighting before rendering if you’re not confidant in your scene or the scene being too large to manage.

This is most likely due to the scene containing too many assets. Unfortunately every project and it's nearly impossible to identify whether or not a scene will run into issues. The obvious scenes are when you have large forest areas & large spaces with many objects in a single view but even then it's hard to tell you will run into performance issues until you finally upload your scene and view it in VR.

The best recommendation for this is sticking to our visual limits shown in the Master Layers

Total triangle count is too high

Total texture usage is too high:

Reach out to [email protected] if you are within budget and crashing is still occurring.

This is normal, when layers are submitted to the cloud we remove them from your scene so things cannot be submitted twice, this also prevents users from modifying their layer. When the layer is processed it will be returned to the scene. If anything goes wrong we store a backup of the layer in a sub-folder next to your max file that we will automatically restore from if the cloud fails to process a layer.

As a 3dsMax artist, you may be used to clearing your hierarchy of layers while using the software. When you are processing, this can remove the layers from your EnvizPro plugin.

As shown above, the image has the 150_BLD_Ceiling Lights layer processing and while this is happening, the plugin will remove the layer from the scene whilst being processed in the background. Clearing the hierarchy (Remove empty layers) while a layer is being processed and the layer will disappear from the plugin, however if you recreate the layer with the same name "150_BLD_Ceiling Lights" and click refresh list it will then return to the listbox.