Page 1 of 1
mxs references versus instances
Posted: Sun May 18, 2014 5:41 pm
by pipcleo
If i need to place 150 copies of a high res tree in a scene which is the best option....
1. Import the geometry then instance
2. use an mxs reference then clone this
3. use an mxs reference then instance this
Using option 2 takes forever to voxellise...
Re: mxs references versus instances
Posted: Fri May 23, 2014 12:34 pm
by Mihai
It's normal for option 2 to take much longer to voxelize, and it will use a lot of RAM, because you are not using instances. The MXS reference lives in an outside MXS, but when it's time to render, Maxwell will load it into your scene and RAM as any other object.
The MXS Referencing is most useful in animations, because you will have much smaller individual MXS files that need transferring over your network. If it's a single MXS, then just use option 1 or 3.
3 will give you a smaller MXS, but if it's only one....don't bother.
Option 3 could be useful also for a still, if you have many trees or very heavy geo to place in your scene. If you reference all of them instead, then you will open your MXS scene faster and you will also be able to navigate your scene smoother (without needing to change the display properties of the trees in case you would be using option 1).
Re: mxs references versus instances
Posted: Sat May 24, 2014 3:52 am
by pipcleo
Thanks for the answer Mihai
If I am correct it is still not possible to instance an entire group , only an object , so instancing a tree group of multiple objects is
still best accomplished with reference object instancing ?
Re: mxs references versus instances
Posted: Sun May 25, 2014 2:47 pm
by Mihai
Yup
