It would check if the attribute layer given as a parameter is actually owned by the drawing, and cancel if not (rather than try and find a layer with the same name).
I've had some success adding a new EFFECTORS depsgraph node in the scene. This acts currently as a backup to supplement individual object->object dependencies and ensure updates in cases not…
It's tricky, because of the indirect relationship between effectors, collections, and the target object (particles). To trigger updates reliably when an effector is added or removed to the scene…
Known issue, particle rotation features never worked well with paths.
Does this need a poll function? I think right now you could call this with an arbitrary drawing from different geometry and it would still try to set the active layer by name. Not a huge issue i guess, but maybe should be handled.
Should probably be moved in the ID section above
@ideasman42 Would be great if you could take a look at this, since you are maintaining the library builds.
Turns out this is caused by MaterialX, which also uses pugixml (1.9). MaterialX exposes some of the pugixml symbols, which then conflict with our own version (1.10).
This can be fixed by…