Anyone tried to import a Poser figure from P6 into Vue6Inf with this hair on??
It's by HarveyMann, terrific hair too!!

The whole thing wouldn't come in, just got a funny squiggle and nothing rendered!
It's absolutely down to this hair, as I deleted the hair in Poser and the figure [V3] then imported into Vue6Inf fine without the hair!
Added the hair again and "poof" gone again!

Any ideas why this particular hair might do this?

I have Kozaburo's excellent hair, and on the one occasion so far that I've imported a figure from P6 into V6I the figure came in fine - but without the hair.

Guess there is some sort of issue with Poser hair in V6.

Haven't had time yet to go trawling the forums to find out how widespread this issue is - because it certainly is one Big Bug!!

Well that's the problem, so far this is the first hair problem I've had when importing from Poser 6 to Vue6Inf, all my other hair stuff comes in ok, there are 2 figures in the image now with different hair that came in ok!!
Weird!!

thefixer - Is the Ultimate hair a cr2 or hr2? I'm just wondering if figures seem to import OK but if you have other things like hair files or props then there may be problems. I'm only guessing here.

It's a cr2, What's odd about this is that nothing comes in at all not even the V3 figure, you can see a squiggle in the preview window but nothing renders!

Once I delete the hair in Poser6 and use a different hair, everything is fine, so I'm wondering what is different with this particular hair!!!

thefixer - I'm wondering if alot of the hair problems inside Vue are due to how the hair is made rather than an actual problem with Vue itself. I've never had a problem with Fabi's hair, this hair also works like a dream in Poser. Now when using other hair like say for instance the Dixie hair or WildHair, then they can take an age to render. Is this because they have just too many strands or the actual file is too large. I don't know, this is confusing me. It now seems that when I create a character I now have to really think about what hair I use because it's not just about which hair looks the best on the character but which one looks OK inside Vue.

Yes I agree, the image I'll be posting tonight hasn't got the hair for the main character that was originally intended, and then I kind of lost interest in the image but I'm gonna post anyway 'cos it took so bloody long to render, not to mention all the faffing about getting the figure to import with the hair! [LOL].

When importing the pz3 do you have Group figures as single meshes checked in the popup window you get when importing into vue.  If not try that. :)

Hi Iloco, no I don't, I will try that tomorrow, many thanx for the idea!

Thee was a problem the same as yours in Vue 5 ing and I can not remember exactly what settings were for it.
 Either check that box or uncheck it if its checked and try.    This may not work in Vue 6 but worth a try. :)

I found a model when saved as a pz3 will not load into Vue 6 but will into Vue 5 so had to make a ticket to tech for it.  Might be same thing causing the problems with hair.

I think it takes ages to render cause of the transmap of the hair; Vue doesn't seem to like much transmap... I'm actually rendering a scene with only one character with "Perfect Touch Hair", I launched the render 24 hours ago, it's still antialiasing the hair!!!!! :cursing:
I wonder if it works faster with dynamic hair, haven't try it yet...

I would think you'd be better off saving the figures separately, and if that doesn't work, you could always use a OBJ export instead of PZ3.
I'm not using Vue 6 - still on Vue 4, but even so, there were sometimes problems like that in Vue 4, with simple (although annoying) workarounds, the simplest being export as OBJ.
If you have favorite textures you use, you can save them to the Vue library after applying them, and after that process, applying them to an OBJ import is alot less tedious.

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.

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.

Or better yet, use Vue as vue, and not as Poser surrogate. The x-Stream thingy points directly in the direction of the serious apps.... 

"in the direction of the serious apps"
MikeJ - Ooohh, now that's below the belt!!
I'm thinking you're being sarcastic here? LOL.

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.

.

It wasn't a shot against you, farkwar, I assure you, and I didn't mean it as such.

As a longtime fan of Vue and e-on, it gets tiresome to see everyone wondering how best to use it with Poser.
I, for one, am happy to see them gaining ground in the realm of serious, hardcore 3D rendering/animation, and am amazed at what they've accomplished with Vue6 and the x-stream plugin for max, Maya, Lightwave, Softimage (?).

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.

"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."

Well, I'll tell you what - I don't know much about the Poser part of Vue 6 xStream, but I think I read something about poses with MT's not being imported properly?

In any event, as a Lightwave 9 user, I've asked  in other forums about Vue 6 xStream, and it is by no means limited to animations. It's my understanding that xStream opens up within the app, and gives the target app access to everything  Vue 6 has to offer, i.e., terrains, procedural mats, atmospheres, .vob files, plants...everything, plus the option to use the Vue camera and lights, or the host app's camera and lights, or any combination, plus being able to combine them in animations.
I'm not using  it yet, but I will be getting it, hopefully soon, 'cause it looks entirely too good to pass up. :)