by jayroth » Wed Jul 22, 2015 11:33 pm
jayroth
Wed Jul 22, 2015 11:33 pm
Understood, but the issue that I have is somewhat different: this asset started with the intention to render in Cinema, and as such had Cinema materials. Next, I had migrated the asset into Arnold, and I was going to render with that. Through some online prompting, I was urged to try Octane, and gradually got the materials (mainly skin and hair) to the point to where I was happy (it didn't take too long). Ultimately, I have decided to render this entire project with Octane, but as a result, I have quite a bit of a materials mess on my hands, which is why I tried the Cinema command (a natural workflow). The fact that the command removed valuable material components was something I didn't realize until just before I wrote that message earlier today. It turns out this has been vexing me for a few days prior, as I did not initially catch the problem.
I appreciate that there is an Octane-supplied method to remove unused Octane materials, but as you can see above, that is not what I was trying to do, and I consider the current behavior as described a bug, and I suspect that most Cinema users would have the same opinion.
I am sure that Maxon would work with you to upgrade the SDK at some point down the line to allow you to correctly handle this case, or perhaps there is already a methodology for doing so.
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!