|
|
Should i use Encapsulate in 3D?
About Truespace Archives
These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.
They are retained here for archive purposes only.
Should i use Encapsulate in 3D? // Tech Forum
Post by jayr // Aug 19, 2008, 1:42pm
|
jayr
Total Posts: 1074
|
I've got a model with a LOT of parts (see here:http://forums1.caligari.com/truespace/showthread.php?t=6299) and i want to save it as one object to load into another scene.
whats the best way to merge all the parts into one object? should i use the 'encapsulate in 3d' button or will this cause performance problems? i don't want my system slowing to a crawl
Also if i do encapsulate it can i still use material instacing with it if it's set to scene mode? |
Post by jamesmc // Aug 19, 2008, 2:09pm
|
jamesmc
Total Posts: 2566
|
If you are not going to move the objects around, just save save as objects.
They will load in the same spot you made them. I would encapsulate like objects rather than a whole scene if it were me. |
Post by TomG // Aug 19, 2008, 3:51pm
|
TomG
Total Posts: 3397
|
One single level of hierarchy should be fine - ie select all separate items and use Encapsulate in 3D. Performance issues only arise when you start to make deeper levels of hierarchy, eg you encaps all bricks for one corner, do the same for the other four corners, then encaps all corners, then encaps all flat walls, then encaps that with your encapsed group of corners.. etc.
So when you get five or six layers deep, you may see performance issues. Before then you will be fine.
You can use Boolean Union if the objects will never ever be separated and moved independently. This avoids the issue of hierarchies and gives better performance - you can always save the scene with all objects separate, so that you have that to go back to if you need to make changes and so on.
Not sure on material instancing, an area I haven't explored so don't know the ins and outs of it :)
HTH!
Tom |
Post by Jack Edwards // Aug 19, 2008, 8:41pm
|
Jack Edwards
Total Posts: 4062
|
The new boolean tool also has a merge option that will make the selected objects one mesh without modifying the geometry. |
Post by jayr // Aug 19, 2008, 10:22pm
|
jayr
Total Posts: 1074
|
thanks guys, encapuslating seems to work fine, the LE would have looked a mess too if i'd have left them all as single objects in a scene!
I did consider using the new boolean tools but i was worried some of the part might have caused issues like not wanting to boolean together, i know i had that a few time with 6.6.
material instancing is a new one for me too, i'll give it a go and see what happens :D |
Post by jayr // Aug 19, 2008, 10:47pm
|
jayr
Total Posts: 1074
|
just an update on material instancing, you can save the 'material' block in the LE as an object and as long as you load your models that use those materials AFTER you load the materials object into the scene all the materials stay intact.
I haven't tried it with muliple 'material' block yet, i have a felling there may be a problem there.
Update: it only works with one material block, the scene doesn't recognise another, it'll let you laod it into the scene but the objects won't use it. |
Post by TomG // Aug 20, 2008, 4:53am
|
TomG
Total Posts: 3397
|
As an aside, the new boolean tools in the workspace side are much more effective than the old Model side ones. While the Model side ones would fail or refuse or give unwanted effects, the new workspace ones are much more robust and run into such issues less often.
HTH!
Tom |
|
