[pipcleo]

Working on a project with many trees using an MXS referenced tree object.....
A question on best practice....
After importing the first mxs reference , should this then be cloned or instanced ?
I have cloned the original mxs reference about twenty times but when I commence rendering voxelisation takes about 20 minutes
and then another half hour to reach SL 0.5.
Didnt try instancing the referenced mxs but the time seems very long on a 120mb total size project.



On a side note the tree I am using was 250 Mb mxs in maxwell 2.6.1.
When saved in 2.7.1 this shrinks down to an amazing 70Mb.
This is an excellent new piece of coding !

[Bubbaloo]

Yes, you need to make a Maxwell clone of the MXS reference or it will treat them all as individual objects.

[pipcleo]

Render time is a killer though..any reason not to instance the mxs reference ?
Will give it a try as a comparison

[Bubbaloo]

It's a trade-off between render performance and memory management. If you run out of RAM, it's worth it to take a hit on render time.

[Mihai]

Working on a project with many trees using an MXS referenced tree object.....
A question on best practice....
After importing the first mxs reference , should this then be cloned or instanced ?
I have cloned the original mxs reference about twenty times but when I commence rendering voxelisation takes about 20 minutes
and then another half hour to reach SL 0.5.
Didnt try instancing the referenced mxs but the time seems very long on a 120mb total size project.

Sounds like a really heavy tree, but shouldn't take that much just to reach half an SL. What are the render times of the tree MXS itself?

If you clone, it should be slightly faster to render than instancing, but it needs to voxelize all those 20 trees.