From time to time I thought about if it would be wise to implement cindigo as a post effect like several other external render engines seems to be implemented in C4D. But till now I'm not really sure if that would give us any real advantage!?fused wrote:I thought about changing the "Render Settings Tag" to an object carrying the settings. Does that make sense to any of you? I think its more useful than a tag, since there are some constellations, in which the tag gets ignored and the settings wont get exported?
Thoughts about it, anyone?
Do you know the reasons about a tag would be ignored if it's implemented the right way?
Apart thereof I have a feeling that Maxon will enhance the possibilities of implementing externel render engines in some way soon. But that's just my presumption.
But yeah, the longer I think about it, why not an own cindigo render settings object (a little bit like the cinema environment object)?
Perhaps even a button which creates a whole working basic setup, like this (potential) new object and also a camera object with a cindigo camera tag and maybe even the execution of a material conversion...
Even better would be a an expedient on-the-fly interpretation of the original cinema materials wherever possible, but I'm dreaming...
