Fluid Vertex Maps Problem Realflow

[Gpix]

Hi everyone,

so, I have an particle simulation with Realflow.

I let generate Vertex Maps for animating a color blend of 4 different fluids with octane.

Realflow names the Vertex Maps for the fluid "weight0, weight1, weight2, weight3".
I read that the vertex maps are name sensitive for the new 2021 octane version in cinema 4d. For the vertex maps to work in an octane material, I have to rename "Vertex-Maps" to " Vertex Map", because if I have in the german version of Cinema 4D the "-" in the name, octane doesn't work with the vertex map.
Also, if I just have 2 different fluids within realflow, the vertex maps that it generate works in octane with a Mix Material, i guess, it is because only one vertex map is needed (doesn't matter in this case, if weigth0, or weight1, both work). So, no problem so far.


But I tried to do it with the realflow plugin and its automatically generated Vertex Maps for 4 different fluids, and I tried to mix them - I tried it with Mix Material, Composite Material and Layered Material - But octane doesn't like the vertex maps. It just doesn't work anything with more than 1 vertex Map.
I tried renaming the vertex maps generated by realflow and removing the numbers and replace them with letters. But Realflow (doesn't matter if cached or on the fly simulation) generates automatically as soon as I changed the name the renamed vertex map new, and give it its original name e.g. weight0.

I've got the feeling, that octane has a problem with the numbers inside the realflow vertex map name. But with realflow you can't change the default output name of the weight vertex map.

So, what could be a workaround, or a solution? Or do we need a bugfix for octane being not character-sensitive for vertex maps?

Thanks in advance for any helpful hint.

Best regards

[aoktar]

You can use Attribute texture(type=float) and enter the vertex tag's name to name parameter.

[Gpix]

Genius! That works!

Thank you, you're the best.

Never ever used the "Attribute Tex Node". What is the initial thought behind its function?

[aoktar]

Genius! That works!

Thank you, you're the best.

Never ever used the "Attribute Tex Node". What is the initial thought behind its function?

For VertexMaps, I'm using an OSL script and having a input parameter which is named from VertexMap tag. But OSL doesn't support special characters, then it fails in your case. But Attribute texture is doing same job with own name parameter. And it supports the any character for names. It's the reason. Now I'm switching to second method in plug side for VertexMaps as a fix on this topic.

[Gpix]

Thank you for clarifying, Ahmet. Going to make the attribute tex node a new companion in my daily workflow!