Forum: Poser - OFFICIAL


Subject: For people who still have Poser 5 installed

Zodo opened this issue on Aug 19, 2005 ยท 12 posts


svdl posted Wed, 24 August 2005 at 4:31 PM

Anything that is set as invisible in Poser is ignored. By default, the ground plane won't be imported. Deleting those extra props can also be done in Vue, as long as they're not parented to a figure. Getting good foot poses on a Vue terrain is almost impossible. I usually use a DNA Microcosm terrain in Poser to give my character(s) something to stand on, then I can get the foot poses exactly as they should be. Another tip: if you're going to do multi-figure scenes, don't import everything at once. Vue then easily craps out on memory. Instead, save your Poser multifigure scene as "All", then delete everything except one character and its clothing, resave the scene as "[character name]", reload "All", repeat the process for all your characters. It's also pretty useful to save your ground figure/prop as a separate pz3. ockham has a python script in 'rosity freestuff that can delete multiple figures at once. Very useful! Then import one of your pz3s, check "Collapse identical materials". Usually you'll want to import a single frame (unless you want to import an animation, or you want to import dynamic hair), usually it's the first frame (unless you have a dynamic cloth animation). Don't forget to UNcheck "Resize and center objects on import" in your Vue preferences! If you don't, every imported object will be scaled to the same height - a child lying on the ground will be exactly as high as a man standing straight (probably not what you want). Fixing up the materials: for skin I set the highlight color to white, highlight global intensity to 20%, and I leave the rest at default values. I connect the bump function to the texture map at strenght 0.02. Materials that use a reflection node in Poser end up as extremely shiny materials in Vue. If the material is supposed to be metallic, I replace it by one of the Vue metal shaders - that'll get rid of a texture/reflection map and saves memory. If it's not and the texture maps are necessary to make the material look good, try setting the "Color reflected light (metallic)" slider on the last tab of the material editor to a high value, 80 to 100%. Materials that effectively only consist of a bump map (for instance, the leather textures by Baron Vlad Harkonnen) can quite easily be replaced by a Vue procedural material that produces a similar output. Saves memory. If you've saved an edited figure as .VOB, you can even use it in an Ecosystem - you can create whole crowds in an instance! A strange effect of Ecosystems is that the size of the objects is halved. You can fix that by setting the Overall scale on the second tab to 2.000 Vue trees are very small compared to imported Poser figures, while other plants seem to be more or less the right size. Scale up trees by a factor of 4 to 7 to make them look realistic. Use native Vue plants, rocks and terrains wherever possible. They're much lighter on resources than objects. In general, Vue is much better than Poser at handling large polygon counts, while Poser usually is better at handling multiple (large) texture maps. A word of warning about closeups: Vue does NOT have a micropolygon rendering option (Smooth Polygons in Poser). If you render a closeup of a Millenium 3 figure, you'll see the polygon edges, no matter how high you set the quality. Render large images to disk. Rendering to screen tends to get you "Out of memory" errors. Vue will attempt to save your scene to a rescue file, sometimes it works. So (like in Poser) save before you render!

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff