Workflow tips for iToo products?

[VelvetElvis]

As we are moving to the cloud for all our rendering, I'm noticing a few things pop up here and there. How do iToo products work with the cloud and what is supported and unsupported? When exporting, the iToo objects are collapsed down into geometry correct? They do not stay live iToo objects such as Rail Clone or Forest?

We use RailClone to scatter our parking lots, but the rendering on the cloud isn't correct. See below for our setup. How could we best set this up to be able to use it on the cloud?

The main setup, it uses the material randomizer to randomize between car paints. The top randomizer has the most popular colors, and the bottom randomizer has the less popular colors. This gives us a normalized distribution of color colors for large parking lots.

The materials



The local render, the cars appear the way they are supposed to be.


The way the cars appear from the cloud, all of the materials are missing.

[dlparisi]

You can't use the Railcone Instancing engine.... Footnote 14: https://docs.chaos.com/display/VMAX/...tedFeatures-14

[VelvetElvis]

Awesome, thanks for the tip!

[VelvetElvis]

Just as a follow up, removing the instancing engine doesn't help for the parking lot set up. It just applies the material ID to the entire car, so that's why it's looking weird. The attached image is from a local render, which mimics what I see on the cloud. In short the cars all use a 20 ID material, and material ID's 1-8 are randomized for the car paint. It also appears that rail clone color isn't supported by the cloud. Does anyone have any ideas on how to best set up a parking lot like this that is compatible with the cloud? I'd like to avoid having a proxy for every car paint for the same model of each car.