By lord.saddler
#323034
When I am using Cinema´s Render Instances (which are correctly converted into MW Instances during export), it seems, that the assigned Object ID Color is ignored.

My current workaround to get usable RGB Mattes is to use Material IDs, which seem to work with Render Instances.

Is this a general issue with Maxwell and Instances, or Cinema only, since I am using internal Cinema Render Instances?
By JDHill
#323042
As far as I know, this is just a current limitation with instances in Maxwell. Also, just so you know, as far as the plugin and Maxwell are concerned, using a Cinema Render Instance is functionally no different than using a plugin Instance object.
By lord.saddler
#323054
Thanks for the info JD! :)

I also noticed no difference between MW/Cinema Instance - the plugin handles everthing fine.

Only drawback so far seem to be the MoGraph Render Instance Clones. With normal objects they work just fine. But cloning parametric objects, or clones of object causes MW to crash or tell me "no instances of emitters allowed".
By JDHill
#323057
Make sure that:

1. there is a material assigned to all objects
2. cloned objects do not have multi-materials

For (1), that would just mean assigning some material to the cloner -- clones will inherit the material. This is related to a bug in the engine having to do with instances of objects which have no material, and applies not just to those made via cloners, but for any instances. For (2), that is also related to a bug in the engine; it just has to be avoided for now, until it's fixed in the next update.

Lastly, make sure that you do not have emissive materials assigned either to instances, or to the objects they instance -- that is illegal in the engine. I used to prohibit this directly in the plugin's code, but for some time, it was allowed, so the plugin was preventing a possibly-useful scenario, and I therefore removed the checks. But it is, at the moment, illegal, and as the plugin is not actively preventing it, it is up to you to make sure this does not happen; when it does, you'll see that message in the renderer.

So, is this a known issue?