When I have imported using the Poser Shaders- I invariably have to spend time turning down the specularity and other adjustments to avoid shiny people. BUT-when I just import with that option unchecked- I get very satisfactory results- in Vue 8,5 (maybe it is different?)
Here is a right out of the PZ3 import-without Poser Shaders checked. What would be the benefit-presuming it does not crash-which is why I turned that off in the first place!

  This is rendered with the 64 bit Mac Beta 8.5 (32 sec on my 1st gen MacIntel Pro Quad)

Can't speak for anyone else but I always use Shaders on import and never have to adjust anything..!!
Also a lot of Poser props, characters are totally shader based, so if you have it turned off you get Vue's interpretation of a texture which is usually very poor.
Example: A skirt prop with Shaders and no actual image map, with shaders unticked it come sin with nothing on it at all, could be you want it that way, but if you want the look of the particular shader it's gonna be all wrong.
I like using the Shader option but I know there are others that don't..

I hate the shaders and always adjust by hand :)

http://www.silverblades-suitcase.com/tutorials/htm/18.html

I avoid Poser all together and just use DazStudio, it has an excellent obj export option, and it is free.

Like Silveblade33, I find the Poser shaders to be utterly useless.

I too never bother with PZ3 import, shader trees or any of that other Poser stuff. I stick with .objs out of both Poser and DazStudio. I always take the path of least effort lol.........

And what a "least effort" it is (;

I'm with 'The Fixer'; particularly when it comes to Poser clothes and hair which have transparences.

 Here is a No Shader Tree direct import and render-the clothing transparency looks fine to my eyes
Is the problem more specialized- which is why I don't see it?

I would suggest you find a clothing item in Poser that just uses shaders instead of texture maps and then import it without the shader tree, see what you get...
IMO, using the shader tree is a must when importing from Poser, for me I can honestly say I've never had the problems these other posters have stated and have never had to adjust anything as far as I can remember.
But hey, it's up to you how you work, nobody can tell you how to do it, do what suits you best..

 Hi TheFixer

  Can you suggest some clothing that uses shaders? I am curious! The reason I have the Poser Shaders option unchecked is that the versions of Vue I have been using tend to CRASH unless I un-check Poser options. Nothing to do with personal preferences!

  I now have a few different builds available including one that I am experimenting with slowly adding back the options.

 My point is that I have been pleased with what I am seeing-so far-with Vue 8's abilities regarding Poser Textures-I am going to experiment (crash test) and would like to know where I might see a benefit

     Thanks!

There is one I have but I can't remember which it is at the minute, I'll get back to you when I find it.

Thanks!!!!!!!! Does this ever apply to skin textures?

You lose most of the nodes apart from the texture maps but most folk tweak the shaders or use SkinVue so that doesn't really matter

Skin shaders don't work particularly well in Vue at the moment, depending who made them.., skin textures on the other hand work fine and don't need any tweaking in my experience.
That isn't the vendors fault, it's Smith Micro and e-on's fault..
They blame each other all the time for failing to synchronise the apps but yea, like Frank says SkinVue is a good alternative and gives excellent results..

If anyone has been following my detailed reports on this, I have been working with a Vue tech at e-on for some time on this issue. Here is one of the replies from the tech I was working with:

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

I have found and reported at least 3 known and verified bugs with Poser imports such as anything dealing with the "Poser Shader Tree" option and "Resizing". As you can tell from the quote above, they have been made aware of the ones I have found and are not able to do anything about it at this time according to their programmers. He explained it was up to Smith Micro because they use an SDK they provide for Poser code in Vue. I asked when they think any fixes may be coming and I got a reply that said they depend upon 3rd party code and it is up to Smith Micro as to when an new version comes out and IF it fixes any of these issues.

At this time, I have seen the "Poser Shader Tree" mess up MANY things, including the skin "blotches" which they reported to Smith Micro. It works just fine in Poser, but when you try to import into Vue using the "Poser Shader Tree" it does NOT translate properly according to the tech. Other issues I found include shaders not looking right, missing, etc. Again, this comes back to the SDK by Smith Micro according to the Vue tech and he reported them.

Since I have found more than several bugs the only thing officially Vue techs said to do to avoid this is to turn OFF "Poser Shader Tree" for all imports and the "Resizing" option too. They said only to let Vue do the materials and such otherwise there will be the issues I reported until Smith Micro fixes the SDK. So basically, that's it in a nutshell. I am surprised it has taken this long for a few of those bugs to be verified and reported by the Vue tech team to Smith Micro. For now, there is no way around these issues though.

Now, more than ever, I am worried that Vue may not be able to be a program I can continue to use because Poser imports are a BIG deal to me for my work I do. When it is unknown when, or if Smith Micro or e-on can work this out it gets very complicated to deal with these issues. I also was wondering why e-on is depending on a Smith Micro SDK and not writing the code for themselves when I believe that C4D does not rely on an SDK and it works great with their "InterPoser Pro".

Hope this helps.

InterPoser Pro is a damn handy bit of code (or at least it was when I was trialling it a while back) but it's not written or supported by Maxon.  It's a third party app.

I'd just stick to importing the figures and then using SkinVue (which does do an admirable job of making skin look good in Vue.)  It does have some limitations (it uses a luminance map to fake SSS for e.g) but then again, Vue is a landscape program not something really designed for doing photorealistic renders of people.  The fact that it does it as well as it does is a bit of a bonus :)

Hi 3DNeo

 This is why I've been leaving Poser Tree off.Thanks again for your efforts!

 I toon using olivier's toon shaders in poser and that way I could import tooned people into vue (clothes and hair and skin).  Complex scenes are too difficult to adjust all materials in vue afterwards when one is making 100s of toon panels.  this now doesn't work properly in poser pro 2010 and I'm very upset and looking at other options (can't find any though that are suitable)
Love esther

 Esther

Sorry to hear that. Daym! Does that have anything to do with your converting your novel into comic form? You must be FRUSTRATED!

  I'll see if I can get it to work. Since we have the same systems (computer and graphics card) and programs-if it works for me-it will work for you. I have had luck importing PZ3's from PoserPro2010 into Infinite 8.5 32 bit if I set the Poser Config to Poser 6. As long as I don't Alyson- or others with the new rigging or parameters(?)

  Are those Mike2 characters? Then you apply the Toon shaders?

                    Eric

those are either M3 or M4 - can't remember now.
 actually I just tried importing a tooned PZ3 into vue 8.5 and it looked perfect.
I had one scene that consistently crashed and then I checked at e-on and the forums and everyone said the poser shader tree import was broken.  But I tried a different tooned scene and it imported with no problems at all.  Even M4 Yago with his magnetized clothes imported perfectly.  so I might still be able to use this.
I've been comparing scenes rendered in poser pro 2010 and vue, and the vue rendered scenes seem to be sharper and with richer colours.  everyone in the poser forum tells me it's the lighting that's messing up my poser render, but I think there's more to it than that. I think there is an intrinsically better renderer in vue.
Love esther

 forgot to say.  Yes,I am still wondering quite how to do my comic (from my novel). I think i will render most of it in poser and then the outdoor scenes in vue and hope my tooned scenes will import and render well in vue.
vue is especially good for crowd scenes.
Love esther

 forgot to say, that render was tooned in poser in a couple of clicks using olivier's toon shaders (art materials from rdna)  with shaderworks, then the tooned pz3 was imported into vue keeping the poser shaders.

 oh I remember another stumbling block. I really like using the conform to scale setting in poser, and that does definitely NOT work properly on import into vue although I can get round it usually by exporting the scene as a .obj but I'll have to see if my poser shader tree comes with it.

 and it's really important with the tooned shaders not to click collapse identical materials or all the textures on the different figures can get mixed up after import into vue.

Esther

 Oh, I thought it was the default toon shader in Poser- I don't have the others so I wont be able to do more than try thedefault  toon shader import

 Side note: do work nights? Or just get up early-it's either late morning or early afternoon where you are.

 it's 1400hr but i do do some nights

 here in sunny queensland.  where do you live Eric?  I'm guessing America.