I have started using Vue with Poser.  I was shocked to find out that a G2 figure with only a shirt and pants on was 5.5 Million polygons when imported into Vue.  Is there anyway to find out how many polygons there is in a scene in Poser before I export?

BTW it crashed Vue when I tried to save it as a VOB.

Any suggestions on how to scale down the number of polygons of figures in Poser so they will work better inside Vue?

Well, I can think of no better starting place for optimizing poser scenes for Vue than Linda's extremely helpful tips: http://www.cornucopia3d.com/forum/viewtopic.php?t=1541

These tips have been the BEST savers of my sanity (and my scenes) when importing Poser scenes to Vue. One thing I found particularly helpful was Linda's tip about ungrouping your Poser file and immediately regrouping it. This will most likely help you successfully save your scene as a VOB.

Also, the last post on this page -- http://www.cornucopia3d.com/forum/viewtopic.php?t=4125

gives tips about optimizing poser textures for Vue before importing the scene (smaller texture file sizes = less strain on Vue!)  :P Poser has a built in python script that can export ALL the textures in a given scene; and many different graphic programs have a function that allows you to optimize them all at once. ;)

Please write back if you have any more difficulties.  :  )

P.S. Even with my "large" Poser scenes, I don't "Create separate Poser files for each figure", as is mentioned in the 1st link. But ungrouping & regrouping my figures & props has helped me immensely... ;)

That polygon count seems extremely high if its only the figures . The v3 character is under 80,000 polys so even clothed its under 300,000 polys.  I have some vue scenes that say over a billion polys and they render ok.

I have a script that writes the full path info to a poser scene file for import to vue ,

http://www.sharecg.com/v/27564/Script/script-to-fix-file-paths

Since that was my first character from Poser I had tried to import, I found the links very interesting.  Also, the comment about that seemed like a lot of polygons led me to do a little testing.  In turns out it was the dynamic hair that was all the polys.

Sydney with Dynamic Hair - 3.5M polys
Sydney Bald - 240K polys
Sydney with complex prop hair - 300K polys

Thanks for the advice.  I will stay away from dynamic hair for the moment especially since my characters were not the focus of the Vue scenes.

Also, the comment of billions of polys has me worried that I don't have something set up correctly because I crash all the time with Out of Memory errors.  I will address that over on the Vue forum.

With Vue, there's an important difference between real polygons and the virtual ones that belong to instances of other objects (which are the only way to get the poly count past a few million without memory problems).

I will admit I freaked when I saw the poly count of a vue scene with a lot of vegetation because my machine grinds very slowly with large Poser scenes but Vue seems to handle it ok, though slowly for renders. I suspect the poly counts are more complicated than they seem , perhaps with instancing . Some of the sample scenes would show if vue is running properly.

I also have win XP with virtual memory set to system managed and at least 30GB of disk space available for it .