It's great that Vue 11 will finally have particles, the missing link in the software for a while I'm sure many will agree.

It's also great how e-on are pushing this and wanting people to talk about it, and rightly so, and I congratulate them on doing both....

BUT....

There are still outstanding issues dating back to version 8.5 regarding memory problems and Poser imports. I have 32 Gig of RAM now, so point 1 is pretty much taken care of for me, but not for everyone..

Now the Poser import is another thing..over the last few years the complexity of Posers shaders and materials has increased exponentially, Vue it seems didn't keep up..problems with Poser imports have been ongoing since version 6, that was the last version that had good Poser import IMO..

Now I'd like to know if these two issues at least have been fixed before I shell out more of my hard earned to get some nice new toys while the old ones remain broken.....

Does e-on actually still want to actively support Poser as a utility for Vue..?

Nomex suit ready for the inevitable retort from the posters who won't hear a bad word said about Vue...

I purchased maintenance plan for a new full year for $195. I love my Vue with all its little problems :)

Mazak

I use 10 Infinite Mazak, and I stand by my previous statement and I also know I'm not alone in that...

Just because Vue is using the sdk, doesn't mean it's using it properly...

Vue lagged behind Poser shaders about 3 years back and have nver caught up, you might not like that, but that's how it is..

While you can't modify them actively, I have great luck exporting from DAZ Studio. I export as OBJs. Then I modify as necessary in Vue and save as VOBs. 

Crashing and issues like that are different. Being able to build and render a scene is, obviously, of the utmost importance. But if one wants to use a program, one often needs to make exceptions. 

Why dont you wait till the PLE is released before you buy it to avoid being dissapointed?  If it doesnt work then just dont buy it.

I import Poser (Pro 2012) into Vue 10 all the time. I hear what you are saying. It's not really an issue with "importation" so much as it's an issue with "implimentation". Sure, the basic geometry and materails get into Vue just fine, but there's so much to Poser's materials that gets left behind. With the complexity of Vue's material editor, I just can't believe Vue isn't able to replicate every single parameter in Poser's material editor. It's just not been implimented...and what has been implimented isn't implimented that well. (You can't tell me that at the very least, Vue can't accurately match Poser's bump and diplacement mapping without adjustment)

To be honest, if it weren't for skinvue, I probably wouldn't use Vue to render Poser figures. I'm seriously thinking about switching to LuxRender for "indoor scenes" as soon as Reality 3 for Poser comes out.

Being able to import/render some Poser content in Vue is a nice feature to have.  But I would hope that Poser users are not buying Vue specifically for rendering Poser content.  E-on isn't really pushing that Vue feature much anymore.

I agree though that SkinVue Elite for Vue 9/10 has given some extra life to the Poser SDK in Vue.

Quote - ...I would hope that Poser users are not buying Vue specifically for rendering Poser content.

Not in my case. I've used Vue since version 1. Steve Bell and I used to bat things back and forth back in the day when E-On actually did real tech support.

That being said, the amount of content available in Poser format is huge and cheap, and the firefly render engine in Poser sucks, so Vue's ability to read Poser files has been a blessing...even though it could be better.

@Shawn, with the advances made with Poser recently, there isn't the same need to use Vue for rendering like there used to be so you're probably right in your assessment. That said Vue still does outside scenes and GR much better than Poser still so on a personal level I still prefer to use it.

@Snallspace..your post 3 above hit the nail right on the head...

Smallspace, you're talking about renderers designed for Poser, not quite the same as Vue, and do all materials come out just as in Poser with them? Talking about Poser materials (not textures) coming in Vue just the same as in Poser is nonsense. No software does that. Procedurals are tied to the engine they are made with, there is no way around it.

That said, Poser imports shouldn't be problematic, and should work as advertised. If it isn't the case, problems should be reported to e-on. o need to report dynamic hair not working though. Never have!

When I use OBJs from Daz Studio, depending on who created the materials depends on what changes I need to make. Those people creating for DAZ Studio are working with their render engine. Sometimes bricks on buildings are too small, sometimes they are OK. In Vue I often have to change the size using Photoshop because scaling doesn't work. This doesn't mean Vue is at fault because the object was designed for other specifications. That said, I have not found an object or a figure so far that I cannot make look good in Vue.

Quote - Smallspace, you're talking about renderers designed for Poser, not quite the same as Vue, and do all materials come out just as in Poser with them? Talking about Poser materials (not textures) coming in Vue just the same as in Poser is nonsense. No software does that. Procedurals are tied to the engine they are made with, there is no way around it.

That said, Poser imports shouldn't be problematic, and should work as advertised. If it isn't the case, problems should be reported to e-on. o need to report dynamic hair not working though. Never have!

LuxRender isn't made specifically for Poser. It's just that the guys who created the Reality plugin made it their mission to be to convert every Poser material parameter into a LuxRender parameter, so when you import from Poser into LuxRender no material adjustment is necessary...just import, set your lights and go.

If a knowledgeable programmer had the motivation and the access to the inner workings of both Poser and vue, I'm pretty sure a Python script...at either end...would be able to do as well for Poser to Vue as Reality 3 does for Poser to Lux.

BTW: Here the Reality 3 link so you can see what I'm talking about.

http://preta3d.com/technology-preview-reality-3-for-poser/

But Vue isn't just an optional renderer for Poser...

But is is used in that way by many....

Largely due to e-on pushing that point back from Vue 4 day, and that Vues lighting is still better than Posers.

@smallspace, thanks for the link, appreciated...

But that still doesnt make it a plugin for poser...

Back in the days of v4 how many other software would bring in poser figures? I doubt many, which is probably why they felt it was worth mentioning it back then.  In all honesty I think they are probably focusing on other things and keeping the support going at a minimal level.

So why not say that, insyead of fobbing you off with BS when you raise Poser related issues to tech support....save everyone the grief..

This thread seems awfully familiar.

No, I don't agree Rich, we haven't reached that point... yet!

I agree ( I know, weird, hun?) with thefixer here about e-on pushing Poser support. They do, it's a fact, whith versions like Frontier, which was entirely written for Poser users.

I wouldn't bitch over materials not imorting right (maybe e-on think that SkinVue makes up for the lack of Poser materials, and I do agree, SV is just fantastic) , but figures and their textures should come in Vue as they do in Poser. If they don't, it's a bug worth reporting.

And what about the Poser shader tree option? Doesn't it work?

I never import PZ3 with Poser shaders.  I just let Vue do its material thing.  My PZ3s are using BMPs and JPGs anyway for textures.

We wanna help and not bashing. I know the Poser shader import isn't perfect. But it saves me a lot time. Poser objects have sometimes many hundred material zones, not all import correct but most of them load fine. It is easier to fix the few materials than import in obj format and edit all materials by hand.
I will contact e-on for more support for poser shaders that is what i can do for you.

Mazak

Thank you Mazak...

I am aware that there are some people still here who want to help.

I do use the shader tree when importing and tweak some myself. My biggest issue appears to be with bump maps being too much when imported...

I have my import set to 0.0001 or something like that, but even then, some of the newer stuff has bumps that are way over what they should be..

Maybe you could recommend some settings for bumps for me..?

I don't remember what bump setting my PZ3 importer box uses in Vue.  I'm back on Vue 9.5 after uninstalling Vue 10.  I adjust the bumps on my Poser figures using SkinVue with a bump value of 0.002.  For water drips, I use a negative bump value with high spec value.  But I rarely use water drips.  SkinVue only works using Vue materials for me and not Poser materials.  It could be because I have Poser 6.

In 30 minutes i must go to work.
Maybe we can collect some Poser import problems in a list. Ok there is a bump map problem, and sometimes we create reflective materials on import. Maybe someone formula the words we will send to e-on?

Mazak

Thanks Shawn and Mazak..

Shawn usefull info on skinvue, I have the Elite version which works really well, sometimes though I need to use the Poser materials.

As a matter of interest, why have you uninstalled Version 10??

@Mazak, I get that reflection thing sometimes too, not often recently though, it adds a reflection map to stuff that I then have to delete...ok, no biggie, but still a time constraint that you can do without...

Quote - As a matter of interest, why have you uninstalled Version 10??

I was working on a graveyard ecosystem scene animation.  Tombstones in the ecosystem would vanish for no reason after rendering about 20 frames.  Then I'd get hit by the blackened frame render bug and Vue would hang.  So I figured I'd just move the camera past those tombstones and continue rendering from 15 or 20 frames ahead from where I was.  Vue crashed instantly.  It didn't matter which frame I rendered at.

It was then that I figured there wasn't anything feature-wise that I absolutely couldn't live without in Vue 10 Infinite.  So I took it off and installed Vue 9.5 Infinite.  (10 was a freebie because I bought 9.5).  I loaded the scene into Vue 9.5 (it said my Vue was older than the file, I clicked OK anyway and it loaded just fine).  I clicked on render animation, and it completed just fine.  I was able to stop and save my progress and continue on rendering where I left off without any problems.  No blackened frames.  No missing tombstones.  I have about 5,000 of them.  My resources were at 75%.

So Vue 10 Inifinite's animation bugs were passed onto Vue 10.5 Inifinite.  A lot of people complained about it in 10.5.  So maybe it will be fixed in 11?  I don't own any Vue 10 content, so I didn't have to worry about 9.5 not being able to open anything like newer trees or houses.

Thanks Shawn, appreciate the info....

I don't do much with animation so it's not an issue Ive seen....it's interesting though.

Hey, calm down, alright? When did I insult you? Never. Apologies are in order.

No they're not..you've always had a go Bruno, so back off....!

The forums are suppose to be productive and helpful. 

I have seen people trying to help or give their opinion on something and get jumped for it.

This is not fair at all as everyone does have their own thoughts and opinions and are free to post it just like everyone else.

If you have a problem with the way someone is talking to you, take it to Admin, not in your own hands.

I am locking this thread as this discussion is now over.