I have some ecosystems and am trying to load 8 mil people and I am getting lots of crashes on trying to import the daz people. I was wondering if I put some of the ecos into a separate layer then make them invisible, would I then be able to load myposer people more easilly? Love esther

Here's a little trick I learned from one of the tech guys and help in this forum.  If you're not going to be reposing the mil peeps, open a fresh scene, import them one by one and save them as a .vob in your personal collection.  Do this for each mil peep you want to import and then close and restart Vue.  Once you do that, you can load each of the .vob's and you should see both a size reduction in the file and more stability in the program.  And don't forget to purge your memory each time you save a peep to .vob.  That way the initial obj goes out of memory and you have better resource management for the next one.

While Vue does prefer .vobs(typically) - since the new version(vue6I) the files sizes tend to TRIPLE in size once converted to .vob- this goes for OBJ/3ds/Pz3's etc etc - I have reported this to tech. 

In addition there is still a memory leak.  What you might could try is using the mil figures as alpha planes or rendering each on a spearate layer - hiding the ones you don;t need & composite in a paint program.

That's really odd because when I converted a I imported a pz3 with V4 and Apollo and converted them to .vob my file size went down.

Vue 6 Esprit
Windows XP Pro
Dual Core 1.8 Ghz Processor
2 Gb DDR Ram

I'm using V6I/ XP Pro/4g ram & all mine have tripled - there are some threads buried in here that mention the same.

There could be a difference between Esprit & Inf ~shrug~ I wish the files sizes did decrease.

So as not to be confusing some do go down and some go up in size.  Why...... I have no idea.  Do some comparing of the pz3's and vob's and you will see this.
 
And exapmle is Faverals Medusa ship with furled sails.  The pz3 is 787 kb in size and the saved vob is a whopping 70.8 MB in size.  The reason I think is if you check save the textures it gets them from poser and stores them in the vobs.  So it can be either way with how the person saves the vobs. :)

Also its confusing to compare what is happening when some people are using Vue 6 Final and some are using Vue espirit which I would think  has less coding in it and it might work different than the version **estherau is using.  But then again I have no idea what she uses.

 I am sure there is still memory leaks in Vue 6 Final with last update and its been confirmed so I will not get into more discussions when its been confirmed and will wait till maybe one day Vue 6 is working as I think it should.

 I too am having problems with big scenes and I have been using Vue since Version 4.  Vue 5 inf is till more able to handle big scenes than Vue 6 at the moment.   I hope this will change with future updates. :)
**

I suspect two things when converting to vob: first, size does increase if you check the incorporate texture maps box, which is normal, and Esprit doesn't allow this, so this may explain why Esther's vob didn't increase in size compared to to pz3
And two, I suspect Vue triangulates all imported geometry, instead of using quads, which adds a lot of polygons, and increases the file size.

One of the options I always use when importing from Poser is to use quads for interpolation.  That may have something to do with it.

No, this actually has nothing o do with geometry, the quaternion interpolation is a method of interpolating animations inbetween keyframes, smoothing out movement. You don't need to check this option unless you import animated pz3's that have strange & unnatural sudden movements that were not visible in Poser.

Thanks, Bruno021.  I didn't know that.

HI, all all lots of useful tips. But now I think the problem isn't really related to size as evenwhen I delete 4 poser peeps from scene and then try and import 3 more I'm getting the crash every time. And that's with 74% of resources free. My original question, I was wondering if it would help the import process to hide some of the things in my scene in invisible layers. I might try that later. Love esther

Yes it would estherau - arrange your layers carefully - then hide what you want - then render only that layer & composite in paint program.

thanks!

Also, if you use Infinite, then use SkinVue.  It's not so much the polygon count that kills, it's the huge texture files.  If some of the people will be in the background, consider reducing their texture file too.  Same goes for the clothes textures - unless it will be very close, reduce the texture size and don't use bump maps. 

that might be what's causing my repeated crashes on import of pz3s as the larger ones are crashing more often, but these imports worked before the latest vue build update. i have intel mac and 4 gig ram love esther

Apart from fact that 6 esprite with latest patch is still buged i find it dont mater save as vob, as it's the polygon count the killer.
I put some poser bit into 6e and took up 200,000 poly and vobed still imported vob as 200,000 poly, so in model program i destryed 140,000 polys and saved and exported as various.
Ya guesed it when imported into 6e it still recognised it as 200,000 poly's so 6 e is crap, i and other users from 5 reported to them about the problems.
Vue 6 was supposed fix this and no it dont so they have no right to portray v6 as use for poser scenes, as thier as no excuse for what they did.
And 1 thing i found with vue 6 beta when import poser bod the materials were high reflection ect, so with full version like with 5 i have to go into materials and bloody fix everything so not bloody impresed.
Same as 5 and it's a bloody pain.