You COULD probably overwrite e.g the preview render preset with a custom one, but I wouldn't recommend it. It's better to have some user settings to open for final output.

Also, you can make a default scene were the settings are included. Vue Infinite lets you make such a scene, that opens as the startup scene.
The lower versions don't have that feature, but you can get it with a little extra work. Just uncheck "Create empty scene on startup", and load your own "Default scene" as the first thing (unless you want another). I have Complete, and use this method. I've also replaced the default atmosphere with my own.

About the C3D items, I've deleted the ~~ files, as Bruno suggests.

I second thd777, that's what I would do.

To the right of the preview images there's a small preview and the text "Free Download" and a link to the various available formats.
BTW: The ones I've downloaded all have the XFR files included.

About COLLADA: It works great for me, from DAZ Studio the figures come in as rigged meshes if exported correctly, and can be posed in Vue 8. The Poser COLLADA export doesn't seem to include the rigging.

Lars "bigbraader"

I second Bruno and hobepaintball, place the objects on hidden layers.

As from Vue 8 the indirect skylighting (skydome lighting gain) takes much more effect. Try playing with this.
Also for outdoor/landscape scenery you should take into account the "optimize for outdoor rendering" radiosity option, if you haven't already.

And more: The render settings differ. A Vue 7 scene imported to Vue 8 with "Preview" render settings will switch to "User settings".
I know this is about Vue 9, but when you come from Vue 6, a lot of things will have changed, like in the examples above.

Lars "bigbraader"

Quote - Lars, those found at Autodesk must be used with Autodesk software, it's in the terms of the usage agreement.

It sounds resonable, but I haven't been able to find such restrictions.

The Autodesk Seek TOS speaks of restrictions in distribution of the files etc. but not for personal use. And why would the Xfrog files be incorporated then, Xfrog is not Autodesk software, so as soon as you use those you'd be violating? 

Update
The ones in the link from "alexcoppo" are also found in the link to autodesk.
I suggest you use alexcoppo's link, since they have the Vue readable formats for them.

But there are many more available at the autodesk site, 100 different species (with 3 or more versions for each.) as opposed to the Xfrog one with 30 species (130 plants). But you'll need to convert them from MAX, MA or XFR file formats.

Really cool, thanks!

While at it, don't forget this one, also posted by me a while ago "100 free Xfrog plants":

http://seek.autodesk.com/search/xfrog?source=QuickLinks&resetft=true

• The mysterious "Frameguides" which very few Vue users knew the existence of :)

Have you tried rendering with the stand-alone renderer (aka external renderer)? If Vue isn't extremely low on resources when you start an external render session, it should run without problems.
Also agree on the pixels/dpi issue, it's pretty poinless to think of dpi in a render.

• Lars "bigbraader" 

Yea, agree with Bruno. Closeup clouds can be extremely slow rendering.

Quote - ... Try bringing in a generic 3D mesh that has nothing to do with Poser. Bring it in with multiple massive texture maps and you'll find zero problems with your scene, animation, moving the viewports, rendering, etc. Download something from scifi3d, Evermotion, Dosch or 3DTotal, or one of the things on the 3D World discs - NOT Poser related things they periodically have on the disc, but cars, tanks, furniture, etc.

The problem isn't texture maps, but Poser and its convoluted file saving and reading system that is a beast all its own. Load any regular mesh and it's textures, no problem.

Don't agree fully. I've had DAZ Studio collada and Sketchup import making Vue crash, the culprit being many and/or huge texture maps. But it's true that it becomes even more fragile when it comes to Poser imports.

Quote - > Quote - An artist can make do with the hardware they have.  Great stuff was created way before there was 64-bit.  If one thinks 64-bit will make their gallery look better, they are mistaken.  It will just allow more of their mistakes and lazy bad habits to creep into their scenes.  More does not mean better.

Hear hear! Let's have superfast machines so that predictable and mediocre scenes can be turned out at higher speed...!

Yep! Agree completely. As I've written elsewhere, most (not all, of course) problems people run into with Vue, are caused by rushing things, being lazy and impatient etc.
Lots of techniques that could still be handy seem to be forgotten, now the Vue comunity purchase their stuff instead of trying to make it themselves.
Hence the artistic and/or technical level flattens, a lot of the "newcomers" can make good looking stuff (based on tutorials and bought items - not particularly original!), but the more experienced users tend to settle for less (on what they can purchase) and not being innovative.
Lars BigBraader

Vue certainly has a problem with huge texture maps in my experience. I often (more and more) use the Collada export (Poser 7), among other things it allows you to downscale the texture maps right away. Also it feels as if Vue "likes" the Collada better, oddly enough.
And downscaling the texture maps is very useful ideed, you don't want a 3000x3000 pixels set of textures for a bird to be used at a small size, or V4 on the half-distance :) It's a waste of ressources any way you look at it. You may be lazy or impatient, that'll backfire! Most problems people have with Vue comes from rushing things and not being careful IMHO.
(I know that you can downscale texture maps in Vue 9, but I don't have 9, and haven't read anything about it, good or bad.)