I've been working in both Vue and Poser (and I'm new).  While trying to import a Poser charater I created into Vue, I get a character with no texture on the head.  Hair is OK as well as the rest of the body, just the head.  I also get this message:

*Unable to locate file RuntimetexturesfaceroomSat_Jul_24_10_30_00_2010Map.png
Would you like to locate it manually?

The faceroom folder is empty.  I cannot find this file. Where does Poser store the face texures?

Thanks,

Cliff

Manually edit the Cr.2 in wordpad so the right texture is referenced

Vue and Poser sort of departed ways with the release of Vue's 8.1 update.  It's almost become an estranged relationship between the two since Vue started dating DAZ|Studio soon after.

Once in awhile, Poser and Vue have to put up with eachother because of their long history together (and because of their fans).

It could be a couple of reasons:

First , make sure you have the Poser import set up right inside Vue..[File, Options, Configure Poser Import]

If that is ok then run the uncompress script inside Poser and make sure everything is uncompressed, Vue doesn't like compressed poser files.
Those should sort out any problems as long as your texture paths are ok..

Also, don't forget the reported bugs that are still known to exist. I was working with a tech over at e-on on these early this year and the problem is still there with no word on when it will be fixed. Those bugs included: Poser texture issues on import, Out of Memory errors and import size errors. All of them were confirmed and reported which e-on said they reported to Smith Micro. The texture issues do NOT happen if you don't import with the "Poser Shader Tree" option. There are several known bugs that if that option is on causes problems with the skin texture.

One thing I learned is e-on does not write their own code for importing Poser models and instead it is an SDK that Smith Micro provides. This I found quite strange since all that is needed is for the code to be written properly by them. Also, other software like C4D does not have these issues with their Poser plug-in so it really is a problem that needs to get fixed by e-on. Please report all findings to them so this will hopefully be fixed at some point.

Ok I'm going to contradict most of what 3DNeo said just there... No disrespect intended 3DNeo..

I always import with Poser shader Tree selected, have never once had a missing texture message, nor have I had OOm's or incorrect scaling on import. From what I've read elsewhere the scaling issue can be attributed to the wrong setting in your options, [1 selected instead of 0.1]

As an aside and a need for more info, which version of Vue and Poser are you using?
Currently I'm using Poser 7 and Vue 8.4 Infinite, although I also have 8.5 which is still buggy.
Maybe 3DNeo is talking about 8.5 which is why I'm not seeing issues when using 8.4....
I don't use 8.5 all the time yet because of it's reliability issues..

Quote - Ok I'm going to contradict most of what 3DNeo said just there... No disrespect intended 3DNeo..

I always import with Poser shader Tree selected, have never once had a missing texture message, nor have I had OOm's or incorrect scaling on import. From what I've read elsewhere the scaling issue can be attributed to the wrong setting in your options, [1 selected instead of 0.1]

As an aside and a need for more info, which version of Vue and Poser are you using?
Currently I'm using Poser 7 and Vue 8.4 Infinite, although I also have 8.5 which is still buggy.
Maybe 3DNeo is talking about 8.5 which is why I'm not seeing issues when using 8.4....
I don't use 8.5 all the time yet because of it's reliability issues..

Just to clarify so there is no false information, my info is 100% correct and comes straight from e-on technical support. As I stated, these are bugs that have been confirmed by e-on going all the way back to Vue 7. I worked with a tech personally at e-on with several issues regarding Poser import problems which was all well documented with several posts on their web site.

This has to do with the "Poser Shader Tree" having KNOWN issues due to the Smith Micro SDK as I discovered and e-on reported to Smith Micro. These are CONFIRMED and can NOT be disputed. Yes, they may appear to work OK, but I have proven to them several broken areas that are not correct with source files sent to them and they verified. In fact, I was the FIRST to report several of these issues and the tech said no one had reported these and few take the time to prove the results in a detailed reports like I did with e-on. One of the problems has to do with the way the SDK tries to read the shaders and translate them to Vue. It may seem OK on some figures imported, but can be seen on others, especially with darker skin tones that appear as blotches.

As I pointed out prior many times, other errors include OOM (Out of Memory) which they also confirmed. It happens at random times regardless of how much RAM you have. The size scale issue is also KNOWN and is a random happening as well. Sometimes it will scale properly, other times it will not. Both Lee Randall and the tech guy I worked with on these issues confirmed this too.

So, as I have reported on e-on, this is something KNOWN by e-on and I worked with them one-on-one for these issues with a tech guy. It goes all the way back to Vue 7 and is a problem with ALL versions they found up to present. It is the Smith Micro SDK they are blaming and not the code in Vue. I was told until Smith Micro releases a NEW SDK for them to try it will remain a problem on several levels. Also, they said the current SDK was going to fix the Poser Pro 2010 importing, but instead broke many things. According to e-on, there is "no official support for Poser Pro at this time" until resolved. Only Poser 7 and Poser 8 are officially supported.

Hope this clears everything up as this was already posted over at e-on months ago.

One way to "correct"  the problem is to do your rendering in Poser, save the image as a .tiff.  Then in Vue create an Alpha plane and click on billboard.  That will flip the plane that will always face the camera.  Then, click on the top image square and load your image, the bottom image square will automatically show the figure mask shape.  You will need to do a little extra work and ensure that the lighting is from the same angle as the lighting in Poser.  The 2D figure generated will cast a shadow.  Jan

**3DNeo...My information isn't FALSE as you have called it.
**Fact is, and it is a fact no matter how you don't like it, I haven't seen any of those problems and I use "Shader tree" each and every time I import my Poser stuff.
You can look at all my gallery and many of my forum posts where I state many times that the "Shader tree" has been used.
Maybe you have problems, I don't...

**Vue 7.x was buggy and did have import problems, IMO versions 8.x have largely seen those problems vanish with various updates.
**One of the reasons I asked the OP what version he was using..
And for the record, Yea I know there are issues with the SDK, I was told that "stock answer" from the e-on techs too..

Quote - One way to "correct"  the problem is to do your rendering in Poser, save the image as a .tiff.  Then in Vue create an Alpha plane and click on billboard.  That will flip the plane that will always face the camera.  Then, click on the top image square and load your image, the bottom image square will automatically show the figure mask shape.  You will need to do a little extra work and ensure that the lighting is from the same angle as the lighting in Poser.  The 2D figure generated will cast a shadow.  Jan

That's sounds like a good idea once I learn how to render using Poser just as good as I can render using Vue.  Do you have some renders you've done using that technique?

What happens, if you render in Poser first? Is the texture found in Poser? If yes, after rendering in Poser, does Vue find the texture, too? (The reason I ask that is, that Poser stores the path information it gets from the scene file (or library files) in its texture nodes until it has to actually load the map. That can be done by rendering in Poser, switching preview mode to texture shaded or via a Python command in Poser 7 and later.)

Hi Shawn, yes--here is one.  Jan

Regarding Shader tree imports, there was a bug in Vue 7.x that was termed the "Hulk Effect" because skin textures used to come out green inside Vue, that was fixed in later versions, since then I have had no Shader tree problems in either Vue 8.4 or 8.5

That is the one reason where the OP needs to answer whether he has at least done the first steps I mentioned to solving his issue, he openly admits to being a noob so let's see if there are noob errors before we go down the road of confusing him with other stuff..

Thanks for your replies...

Uncompressing does seem to help with my problem with most characters -- now I'm out of memory on others after fixing the texure issue.   Poser was great is fixing a previous problem with the talk designer. 

I wonder if trying all this in a 32bit environment is part of the problem...

Cliff

"What happens, if you render in Poser first? Is the texture found in Poser? If yes, after rendering in Poser, does Vue find the texture, too? (The reason I ask that is, that Poser stores the path information it gets from the scene file (or library files) in its texture nodes until it has to actually load the map. That can be done by rendering in Poser, switching preview mode to texture shaded or via a Python command in Poser 7 and later.)"

I did work earlier in both Poser 7 and Vue 7 and had few problems putting them together.  Yes, I do render in Poser 8 first, them save and go to Vue 8 and import my character. 

Cliff

If you're using 32 bit my guess would be that you don't have sufficient RAM to do what you want to do. If you could give some detail on what you have as a system it would be helpful.
Generally these days Vue needs a 64 bit system for any serious work IMO..

Quote - If you're using 32 bit my guess would be that you don't have sufficient RAM to do what you want to do. If you could give some detail on what you have as a system it would be helpful.
Generally these days Vue needs a 64 bit system for any serious work IMO..

In Vue Infinite 8.0 32-bit build 47776 I can import six Poser 6 PZ3 figures into a default Vue scene, rendering with Poser 6's materials and SkinVue 8 enabled before I reach the end of my RAM (2GB).

In any later build of Vue Infinite, I cannot even import any of the Poser 6 PZ3 figures without OOM errors and crashing Vue.  My Poser 6 is up to date.  Poser 6 never crashes on me and neither does my Vue Infinite 8.0 build 47776.

If e-on ever decides to add shadow catching to Vue, I may update my Vue and then just use alpha billboards for my figures (they're just for populating a scene anyway and not the main focus).  But e-on isn't interested in the "match-moving cameras with AVI footage inside of Vue" market.

Quote - **3DNeo...My information isn't FALSE as you have called it.
**Fact is, and it is a fact no matter how you don't like it, I haven't seen any of those problems and I use "Shader tree" each and every time I import my Poser stuff.
You can look at all my gallery and many of my forum posts where I state many times that the "Shader tree" has been used.
Maybe you have problems, I don't...

**Vue 7.x was buggy and did have import problems, IMO versions 8.x have largely seen those problems vanish with various updates.
**One of the reasons I asked the OP what version he was using..
And for the record, Yea I know there are issues with the SDK, I was told that "stock answer" from the e-on techs too..

I must say that you are giving out FALSE information here. Yes, it may work for you, but that does not negate the fact I have documented several known bugs as stated and they have been OFFICIALLY confirmed by e-on as KNOWN problems now. This is not just something I am saying because I think it is so, this is something that was PROVEN. Now, if you want to believe you know better than e-on and the tech guy working on the code that confirmed my reported bugs and was PROVEN to be problems, then I think you may want to retract your comments.

Again, all of this was well documented over on their web site long ago and I was the first to do extensive testing with their tech on this. Here is one of the OFFICIAL reports straight from the source:

"*I tested your model and noticed that these blotchy patches are also present in Vue 7.5. In Poser, the material editor shows that the diffuse color is the result of a blend of two nodes (image map + spots). In Vue, those spots are too dark. As the materials are rendered using the Poser Shader Tree, I reported this bug on the Smith Micro bug base.

One thing you must know about Poser imports in Vue is that it mostly depends on an SDK (Software Development Kit) provided by Smith Micro. It's a black box that allows Vue to have some functionalities of Poser. The latest one was added in Vue (build 51713) to fix the annoying "Hulk Effect" that several users reported (and complained about!). It was also supposed to bring support for Poser 2010. Instead, many users are now very upset because other bugs appeared (crashes, OOM errors, Poser features not properly functionning...etc).

It is best to leave "Poser Shader Tree" turned off.

Best regards.
Nick Deafman*

My system:

Vista Home Premium 32bit
Intel 2.66 Quad Core
Nvid 8800GTX
4MB DD2 PC6400 (3.1 reporting)
Poser 8
Vue 8 Esprit with Hyperview and  KronosFX Add-ons

3DNeo...I don't want toa rgue with you, maybe you need to re-read my comments..
I know there are bugs, I said as much when I said about the "Hulk" effect, that doesn't change the fact that as usual some people have problems and others don't.
As for e-on "blaming" SM for the SDK...SM "blame" e-on for the problems, I guess it comes down to who you believe.
If you want to believe e-on that's up to you..
And as for your letter from the techs, I had a different one saying nothing about switching shaders off, and why would I, they're not a problem for me...

My concern is helping out the OP and to begin with we need to see if he has made any noob errors before going down other routes to help him. If you want to argue I suggest you take it somewhere else, I'm not interested and I will retract nothing because all I've said is factual.. E-on have a habit of fobbing people off with stock answers, if you don't know that by now then you need to go back and take a look at other support tickets..

Shawn.. I agree Vue 6 Infinite was by far the best, but IMO 8.5 is getting close now..

Mavrick...Specs look ok, did you do the suggestions I made, like configuring the Poser import in your Vue options??

Maverick...This is a link to my latest image rendered in Vue 8.4 wirh Poser shaders, you can see quite clearly that there is no issue with the shaders..
If you look through my gallery, every image with a person in it or without, if they have Poser imports, the shaders are used each and every time..
The "Hulk" effect in Vue was cured ages ago and is a red herring in this conversation..
Please attempt my original requests first and see how you get on then..

http://www.renderosity.com/mod/gallery/index.php?image_id=2103435

Mav 

Next question then, does this happen with every skin texture you have or just with this particular one??
Can you tell us which texture this is??

On further experimentation, it seems to happen on faces that have been to the face room.  Stock figures always come out OK.  Although I thought I told Poser not to change the texure, (only shapes) maybe I did and the texure difference between body and head is the issue.

Mav

When Poser importing was broken inside of Vue for me, it didn't matter if I was using Poser materials or not.  Vue still took a dirt nap.

I forgot to mention that when Poser (PZ3) importing was broken in Vue, exporting my Poser figures as OBJ and importing them as OBJ into Vue caused the exact same OOM errors in Vue as when I imported them as PZ3.  So I don't think the Poser SDK had anything to do with it.  Vue just has a broken importer in general.

Mavrick...I've never used the faceroom before importing, I genereally use the DAZ figures, this could be a cause of your problem..The faceroom texture is never good, even inside Poser.

Another tool you should get is a little programme that used to be in freestuff here called "Correct reference", it checks the paths of your texture files inside Poser, if any are wrong it will correct them. There is a better version that you can buy, but for checking and fixing texture errors inside Poser, the free one works just fine..
I can't seem to find it at the moment though, perhaps he's moved it to somewhere else.
It was by a guy calling himself "hogsoft", he doesn't show as a merchant either so I'm not sure if you can get this now..
Maybe someone else knows where he is or where his utility has gone to..

Thanks for the advise.

I'm having to start over with my characters.  Instead of using faceroom, I am morphing the head and face directly from the parameters tab. I tried some test imports into Vue  and all seemed OK .  I have thought about going the DAZ route, but some characters will be moving and speaking.  In Vue, I have made a number of sets where the characters will be placed.  I will check the utilities, seems like a good tool to have.

Mav

You're welcome,* * hope my advice was helpful, it sounds like it was...