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.

Jeff

Development on: Mac Pro 2008, Duel-Boot OS - Snow Leopard 10.6.6 & Windows 7 Ultimate 64bit, 2 x 2.8 GHz Quad-Core Intel Xeon , 10GB 800 MHz DDR2 RAM, NVIDIA GeForce 8800GT.