Quote - "Poser's content library has Poser or Poser Pro as a gateway. Write a means of importing Poser content into LW, and what do you need Poser for?"

That is exactly what Daz is telling everyone with Carrara. LOL.

Could also be one of the reasons why EF is doing the pro thing. I don't know, it's just a guess.

I have not been paying a lot of attention ot Poser Pro since it is not out yet but this feature sounds very much like the import we get with Vue (and with Shade though I don't do that very much) from Poser. You get the ability to import Poser models and animation into Vue. You can enable the ability to pose the models using Poser inside of Vue. Vue warns you that it takes up a lot of memory because you are really running Poser objects. So what is the use of Poser? Everything! It is what you are using to manipulate the objects from Poser.

The 10 node rendering... could be cool if they get the animation tools right. Some of that seems to be coming with the fact that EF now has several of the components that they need in different apps. Consider this:

1. Shade 9 suggests an atmosphere model perhaps via Vue.
2. Shade/Poser seem to be getting closer (along with Vue hopefully) to allow passing scenes across the 3 apps.
3. Vue has a plug in called Ozone that runs in other apps... Poser, seems to be becoming a series of components that run in other apps for Charater Animation as well as an app in itself.

So... If you use Shade/Amapi to do the modeling and Ozone in Poser (someday) to do environments then the 10 node rendering becomes huge!

The way I see Poser Pro is positioning... Shade/Amapi/PoserPro become a series of component that are purchased as needed and added to a base application (Poser).

Also, the comparison sheet is the "Base" version of Poser Pro. There are several Add-On that will be available that will hopefully make the product much more useful.