How Heavy is a Geometry Shell?

AndYourLittleDogToo

I would like to implement an Ecosystem-like function where I can create many geometry-shell instances of a mesh, and make them all different by hiding, showing, and recoloring certain material zones through a script. If a geometry-shell instance is pretty lightweight -- that is, it contains only the individual material information for each zone -- then this would work quite well for making interesting cities and forests. If these instances are much heavier, then this might not work out so well. How much information does a geoemetry shell contain?

cwichura

Why not use actual instances instead of shells?

Jaderail

Both versions are Lighter on the RAM than a true mesh and only Geo-Shells support multi textures. The Render engine will still see the SAME amount of Mesh at render time so be ready for the HIGH mesh count render times. Other than That I see no reason it should not work for Cities, I use Geo-Shells for my forest sets all the time.

This way I can use different Textures on different trees. A Instance is a 100% copy and not changeable like a Shell.

AndYourLittleDogToo

Jaderail said:

Both versions are Lighter on the RAM than a true mesh and only Geo-Shells support multi textures. The Render engine will still see the SAME amount of Mesh at render time so be ready for the HIGH mesh count render times. Other than That I see no reason it should not work for Cities, I use Geo-Shells for my forest sets all the time.

This way I can use different Textures on different trees. A Instance is a 100% copy and not changeable like a Shell.

Jaderail,

Thank you. I'm glad to hear that a shell is pretty light. I'll go ahead and give it a try.

Jaderail

I did forget to mention this, each texture or shader you use will eat RAM, so be sure you have enough free RAM to render the image with.