The .ru tells you it is a Russian site, a Russian domain.

You are not going to get any relief over there, from here.

For the last 80 years if anyone over there wanted anything good they had to get it on the blackmarket by piracy and violating the law.

You can threaten them all you want, they are not afraid of you or what you can do(which is next to nothing).

The new freebie, Anarane, from DAZ crashes mine on import too.

I looked in the PZ3 file, but nothing stood out as offending.

Am I missing something about 'spectral clouds'?

They seem to be only large spheres with volumetric cloud textures applied to them.

I was doing that already before.

/scratches head

What is different about them, then just a bunch of pre-made spheres with clouds and stuff added to them?  I feel like I am missing out on something.

http://market.renderosity.com/mod/bcs/index.php?ViewProduct=25602&

Thanks for making me check it.

In Poser's runtime, yes.

In my runtime, no.

Mike,

Even if it were(a shot against me), I am long long passed the time where I could be offended by anything.

Vue is specifically designed to integrate with Poser, actually.  It has its glitches, mostly because they are, at this time, two separate software houses.

I can tell you that the amount of work that is involved with bringing Poser figures, scenes, and models into 3DStudio Max is absolutely unbearable.

And I don't think that everyone who is taking on Vue6 is taking on the XStream version.  I would assume very few, actually.

Vue's ability to render Poser scenes is remarkable(far superior to Poser, of course).  Much more than any other outside app, honestly.  Vue now has integration for Poser shaders, as well as positioning of figures along Poser bones.  You can reposition figures in Vue directly now, that is a major and notable breakthrough.

Correct me if I am wrong, but XStream is mostly an animation integration, much more than a rendering companion.  Most amateur artists who are using Vue, are going to be using it for stills.  They don't really need XStream.

The glitches aforementioned are in how Poser 7 now writes its PZ3 files.  It truncates the path to the object mesh file.  And as such Vue can not find it.  Poser is writing the path to the textures just fine.  All I was offering was a workaround until P7 is fixed(if it has not already been), such that users could still use the PZ3s.  It requires some confidence in editing long assed text files, of course, but when they are edited, they will import just fine.

After that, they are up to their own devices, as to what art they want to produce.  Good, bad, or ugly.

Well, if you have a modeling program you can create the models that you need.

Then you can render them in Vue.

You may be able to get what you want with Vue primitives, like cubes and such, but without a real model creating package you are going to find that frustrating, most likely.

There are a couple of expensive such programs on the market, and some free ones, Wings and Blender being the free variety.  I think Hexagon might be available for very cheap.  And Silo used to be free for a demo, or such(I don't know if they still even make that one though).

ZBrush is a powerful tool for modeling as well, and inexpensive for what you get, but I don't think you really need something like this, for what you are after.

In poser, you need to go to preferences and turn off external morph targets.

It is storing the morphs and pose stuff in a separate file, which Vue does not look at.

A typical render from Vue will cost me at least 1.4 Gbs of memory.

A typical external render is between 600 and 800 megs.  It appears to be more conservative.

Vue is pointing to Poser.

The built in Poser Shader importing is an obvious example of this

Not everyone is a professional artist, Mike, like yourself.  And most do not actually have to have Maxwell or 3DSMax on their resumes.

Art is what one produces.  And the manufacturer of the paint or the brushes does not add to it, not one bit.  Do you know what brand of chisel and hammer Michaelangelo used?  Do you know what brand of paint Bosch used?

Now, most artists here are clearly amateurs, like myself, and are not professional artists, like yourself, so one my analogy to the masters is only a rough one, and two I am pretty sure that everyone here is using Vue as intended(or at least intend to use Vue as intended).

Not all of us have the time to walk up the learning curve of modeling in 3DSMax or lighting and shading of Maxwell; and this product produces some remarkably clean drawings, with much less invested time in learning the tools and interface, if you were to ask me.

Now if I were a professional artist, and that day may come, I will indeed put 3DS or Maxwell or Lightwave on my resume.  Until then, I will use the tools, brushes, and paints which give me pleasure making the drawings I am making.  And I would hope, that even as negative my posting style generally is, that my posts here do have some positive insight for the readers of them.

.

The external renderer will use far less memory than Vue does.

It will use 100% of CPU though.

And Vue may be shut down, or used for other purposes while the external renderer is running in the background.

It will also store future renders in a queue, and render them in a row unattended.

It will generate an alpha mask, a z mask, as well as the image.

Just change something that looks like this...

prop ws_rail_1
    {
    storageOffset 0 0.3487 0
    objFileGeom 0 0 :Runtime:Geometries:RHS:Wall_Sections:ws_rail.obj

To this:

prop ws_rail_1
    {
    storageOffset 0 0.3487 0
    objFileGeom 0 0 C:3DRuntimesSetsRuntime:Geometries:RHS:Wall_Sections:ws_rail.obj

Just add the the small part that is needed so that Vue can find your object files.

Fixer is gonna hate me again for saying this.

But open up your PZ3 in wordpad and type in the full path of the object at the object call lines in PZ3.

There is nothing mysterious about the PZ3. It is just a large text file.

Save as psd is my recommendation.

You are going to be using that format already, might as well make it native.

And if you don't, then use tif for your original save.  It is a compressionless and lossless file format.(most of you probably already know that, though).

nm, I think I figured out what I was doing wrong.

Thank you for the steps.

I just did not have enough contrast in the mask.