[micha908]

Hi,

this is a small bug, but the Volumetric tag does not recognize the Alembic object as a valid object and does not show its settings. I'm importing a point cloud through Alembic into Cinema, and the Cinema Alembic object automatically creates an internal Particle Geometry object (when Points are imported as Particle Geometry in the Alembic import dialog). The workaround right now is to create another Particle Geometry object and use that with the Volumetric tag, but it should not be necessary (and it isn't: when you make your settings in the tag, you can then drag it onto the Alembic object and delete the superfluous Particle Geometry object, and Maxwell will render it fine).

Cheers
Michael

[JDHill]

Thanks for the report, though I am not clear on one point, regarding where you say the tag "does not recognize" the Alembic object: the Volumetric tag should be telling you in the AM "Invalid Parent: This tag is only valid on Null, RF Particles Importer, and Particle Emitter or Geometry," whenever you place it on an object not in that list. That is what it is doing, correct?

[micha908]

Hi,

yes, that is indeed what it says. So I assume it just has a list of object ids that it checks the parent object against - to which the alembic object should be added, at least if it is in the "Particle Geometry" mode.

Cheers
Michael

[JDHill]

Thanks, I just wanted to be sure there wasn't something strange going on. On what it will take to support it, it's a bit more complicated than just adding it to a list, what with the plugin supporting R9.6 and up, but yes, it's something along those lines. The reason it works when you transfer the tag manually over to the Alembic emitter object, is that in the representation given to the plugin, that object actually is not represented as an Alembic object, but as a particles geometry object like any other.