Glitterati3D posted at 8:34AM Fri, 28 June 2019 - #4355078

EClark1894 posted at 6:41AM Fri, 28 June 2019 - #4355071

ironsoul posted at 4:28AM Fri, 28 June 2019 - #4355066

wolf359 posted at 6:02AM Fri, 28 June 2019 - #4355004.

To move forward I think we need an upgrade path that allows old FF content to still be used in poser reliably.

I actually would have no real issue with that since we technically have three renderers in Poser now. But implement a full Cycles now. With all the nodes, and Cycles shader development should expand. Right now you can only do so much, and places that make shaders for Cycles, don't bother with Poser's limited nodes. It would also help if Poser could read Blender nodes since they would do the same thing. But there's not much point if the nodes aren't in Poser.

Wow, so yeah, now you want vendors to add yet another render engine to learn and support. I hope you're willing to pay the additional price for products to support all this work?

Not if you're going to be charging exorbitant prices, I'm not. Besides, the render engines are already in Poser. And after two whole years, I'm not asking you to learn anything you should already have a handle on by now anyway.