Hi all,

I created a big object in Hexagon and exported it as an .obj file for use in Vue.

All works as it is supposed to but the .obj file is a whopping 162mb and this works very slowly in Vue.
It even works slowly in Hexagon due to the number of polygons :-)

When you guys and girls create an object, do you decimate it before use in Vue ?

Thanks
Wim

WOW man, as a new modeler myself I must say...that is HUGE file size. I made a model with 220,000+ polygons which of course Vue imported fine and after the .vob export it was only 80Megs, which is rather large. Maybe you should look at the way your modeling to start(; As for decimation, well it depends on what it is, i havent had any luck with it in Cinema, but Hexagon i know nothing about. I did learn very fast though, it is VERY important to get a routine and learn tools and model the same thing over and over till you learn all the shortcuts :D I have the exact same model for comercial use down to 87,000+ and nothing different at all.

If you double click on the object in Vue, there will pop up an option to decimate it.   Or....

Hexagon has a good decimator that leaves nice sharp edges. Good for tech stuff.

AccuTrans is a very inexpensive (20bucks) 3d object optimizer. It can also translate tris to quads.

Then, last but not least there's Blender which can do both and more.

I've been known to run ZBrush meshes through Hex to decimate them before I load them into Poser or Vue - so long as you don't overdo it, it works pretty well

Perosnally, i wouldnt let Vue decimate it. Vue is not a modeler..and Blender...well free yes and cool i am sure from what i seen, if you can get your head around that gimme a call :D ZBrush...well forget about it...what a waste of cash...Only interface i know of that could enter the special olympics:P Thing is, learn your tool and get the best most acurate mesh you possibly can before loading into Vue, then let Vue deal with it, cause it is gonna turn it all into tris anyway(;

 One of the drawbacks of subdivision patch modelers, is they create objects with tons of polygons. This is one of the reasons I prefer modeling in SketchUp for many things.

One thing you can do, is export your mesh at a very low sub-d patch setting, and let Vue add the polys for you during rendertime using the Dynamic Subdivision feature in the Polygon Mesh Options panel.

Quote - Hi all,

I created a big object in Hexagon and exported it as an .obj file for use in Vue.

All works as it is supposed to but the .obj file is a whopping 162mb and this works very slowly in Vue.
It even works slowly in Hexagon due to the number of polygons :-)

When you guys and girls create an object, do you decimate it before use in Vue ?

Thanks
Wim

I never decimate.

Something is wrong there.  Either you hit smooth more than twice on an already smooth model, or you've been exporting/importing the model as OBJ using Hexagon and not saving it as HXN which would reduce the file size greatly before exporting it as OBJ just once for Vue import.

I dont know Hex well, did you use splines to model the pillars ? Yu can get away with primatives at lower poly count if its not gonna be to close up of a render. Looks good though(;

Not shure what splines are but as far as the balcony pillars go, i created a square line and a circle, linked them together on four corners with another 4 lines and ten i used 'gordon surface' which creates a surface from a network of curves.

But for the most part of the model in it's entire (the temple itself) i started out with primitives.

Splines do the same thing. Create a surface (and a ton of polygons) from a network of curves :D

Same thing i suppose(; As i said, i am new myself, so i could be wrong...

I'm busy texturing it in Vue and this is howit looks so far.
Please don t' mind the lighting  and composition yet LOL ...

If this object is intended for use in vue only, and if the main problem is with the pillars on the balcony, you might want to consider using the pillars as eco instances rather than one large objects.

1. remove the pillars from the big object
2. make one pillar object
3. make an object (or material group) that defines the area where the pillars should be (3 rectangular shapes) (I'll call it 'shape')
4. import the main object and shape object to vue.
5. Make the shape's material an eco material, use your pillar object as 'instance' and populate using 'force regular alignment of instances'. adjust density to get the spacing right.  If small additional adjustments are needed for precision placement, convert instances to objects, adjust and restore to eco.

When finished you can save as vob
It saves a lot of resources to have items as eco instances rather than objects.

File size does not equate to polygon count.  Once the huge file is imported into Vue, you may be able to save as VOB and end up with a smaller file size than what the OBJ was.