Thanks for your help! Your reminder to check the object path brought me to the solution: I still had declared the Poser6 directory in the import option and since I had to install V4.1 in the Poser7 native directory (and not in an external runtime like V4.0) Vue didn't find it. 
The problem is that you need Version 4.1 if you want to use the muscle morphs (and I guess the creature morphs and probably all morphs and additions that DAZ is going to publish over the next years!). 
Thanks again!

Sebastian

I have another problem with V4.1: I can use her in Poser 7 normally, but when I import her into Vue6I she is missing. All other props and figures (like hair and clothing) appear normally from the imported pz3, but the V4.1 body is missing! I can use Victoria 4.0 without problems. I tried redownloading the files, I tried saving the figure to the Poser 7 library and reloading it and I switched the external binary morph targets on and off - no effect. Has anybody encountered a similar problem (and maybe found a work-around)?

In case you are using Poser with Vue, there is a software called Weird Juice. It is a python based particle system that also uses metablobs, so you can create realistic (and animated) water flows and fointains. I used it several times and it always imported nicely into Vue.

http://www.weirdjuice3d.com

I just sent it to the support. I was hesitating to go back to Vue5, since there are a lot of nice things in Vue6 that I already got used to (like REAL units). But I haven't been able to finish more than one image since I have Vue6 (and that was a hard fight). All the other times Vue6 just kept on crashing... Guess I have no choice.
I should add that I have only 1 MB of memory, which is certainly not enough. But it was OK for Vue5, so I thought it would also be enough for Vue6.

I just discovered something surprising (at least to me):
I saved a figure in Poser 6 (Victoria3 with some clothing) and imported it into Vue6Inf and Vue5Inf. After the import I saved the file without manipulating the imported object. What surprises me is the following. The File saved in Vue5 is 45 MB big (almost exactly the size of the pz3 with 48 MB), while the Vue6 file is 170 MB big! No idea what additional information Vue6 is saving into the file.
By the way Vue6 crashed shortly after saving while Vue5 didn't have any problems with the file. sigh

Thanks for your answer. I'm using Vue5Infinite. I know about the MP-Buffer, but I didn't think it would help. But maybe you are right - when I just render a single object, maybe in photoshop (or GIMP in my case) the rest of the layer will turn out transparent. I will try that out. Thanks a lot!

Sebastian

I found out that I can sometimes crash vue by moving one object from one LAYER to another. Nothing changes in the scene, just the layer to which the object belongs to. I don't know what vue is doing then, but apparently it needs a lot of memory for this process...

I didn't have the impression rendering to disk is much of an advantage anyway. And since you can't render areas (why?!?) it is actually quite a disadvantage. It must be a problem deep inside the algorithms of vue. I was able to render huge pictures without any problem and with lightning speed as long as they contain only vue native objects (like plants). I guess the problems only became visible when people were starting to import poser objects with their huge texture maps. And the error seems not even to be reproducible. There is an area of resolution in which vue crashes SOMETIMES (render the same picture, one time it works one time not). I'm afraid e-on is not going to be able to fix this bugs in the next times. I guess you also tried that, but what helps is restarting vue or even the computer before rendering. That clears the memory. But it only helps to get you A LITTLE MORE resources. I guess it is not enough for you.

Since I have only 1 GB of RAM I often run into this resolution problem. I found that I could go to higher resolutions by rendering smaller pieces of the picture (with the render area option) and putting them together afterwards in a photoshop-type program. I don't know how far you can push it with this method and it is a pain in the ****, but maybe it helps.

Kodesign has a nice package here at the market place featuring a snowbug, a millipede and some more. The creatures come with easypose technology and are easy to use.

Attached Link: http://market.renderosity.com/softgood.ez?ViewSoftgood=18033

Had the same problems. But once I updated Vue everything was working fine.

I have used the Weird Juice particle system (also from DAZ) for Poser and it imports into Vue without problems.

I have the same problem with a few files. I didn't find any pattern which files don't work. The only thing I can do is apply them manualy afterwards in the material editor. Funny enough, Vue doesn't have any problems then using the image as texture map. It is just a problem when importing it.