jennblake opened this issue on Jun 20, 2019 ยท 654 posts
JohnDoe641 posted Thu, 27 June 2019 at 11:48 AM
Afrodite-Ohki posted at 12:28PM Thu, 27 June 2019 - #4354969
The thing with Superfly is that it can read previous Poser material nodes - with very few limitations. You can use nodes you're used to, nodes that do some things there are no specific Cycles nodes for, etc. And if you load old props, you don't really need to remake every material for Superfly - it'll treat diffuse color/textures as a DiffuseBSDF, Specular color as GlossyBSDF etc.
Ditching Superfly to go full Cycles means breaking a LOT of previous content, AND forcing everyone to use a Cycles Root node to use it.
While it's true that a lot of content would have issues, I mentioned that there needs to be an auto-script that would convert certain materials to Cycles. If Reality was able to convert materials to Lux then it should be possible to have something like that for Cycles, just integrated within Poser with an easy to use one or two click operation.
What other choice is there? SM had over a year to get SF compatible with Turing, but nothing ever came out of it and as of now it makes SF a dead end and a major problem for anyone looking to upgrade their GPU from Pascal. You saw the threads that were starting to become common on the SM forums, every week there was a question of why someones new video card wasn't working for SF and the answer was always the same.
I don't know if SM was unwilling to add that functionality to SF or they simply couldn't due to SF's implementation, but I don't think SM would purposely not add in functionality that would extend Posers life cycle. So I'm assuming that it's technically not a feasible feat with what we have right now. Though I'd love to be proven wrong and have a new update for PP11 that gives us support for Turing cards because being forced to use old hardware that's become even more expensive than the newer hardware is pathetic.