jennblake opened this issue on Jun 20, 2019 ยท 654 posts
Glitterati3D posted Sat, 13 July 2019 at 7:27 AM
And, I agree with perpetualrevision and estherau - keep both render engines. But, stop with Superfly/Cycles and Firefly. There's only so much the vendor community can support, and engines like Octane and Luxrender have always been "cook your own textures" render engines.
The only caution I offer about Cycles is that the preview window HAS to display the materials. On things like clothing, not so much, MAYBE. But, you cannot expect a user to select makeup/lipstick/hair color options on a product that doesn't preview those options. If the library images were larger, it might be viable, but with a 100x100 png file, there's no way to know what makeup options look like if not displayed in the preview window.
I do think keeping Firefly is vital to the part of our community that isn't interested in realistic rendering and hope the DEV team honors their work by keeping it viable.