OTOY Forums

Every single time I connect an instance color node to my materials, then select particle mode, then insert my Xparticles emitter as the color source; I get an "Octane:<<< Mat checkANDUpdate STARTED >>>" message, and C4D freezes up. I've never had trouble in the past, but I'm not certain that I am not the problem. I'm wondering if anyone else has a similar issue within the last few builds with Xparticles. Thank you.

cannon126 wrote:Every single time I connect an instance color node to my materials, then select particle mode, then insert my Xparticles emitter as the color source; I get an "Octane:<<< Mat checkANDUpdate STARTED >>>" message, and C4D freezes up. I've never had trouble in the past, but I'm not certain that I am not the problem. I'm wondering if anyone else has a similar issue within the last few builds with Xparticles. Thank you.

Could you give us your scene which is locking when we connect it?

aoktar wrote: Could you give us your scene which is locking when we connect it?

Thanks for the response aoktar. I would love to, but this scene is under NDA, is there any way to do it privately?

Maybe I can take some time today to recreate it with some dummy geometry. I'm just under a time crunch, and moved to Redshift for this scene...which believe me, is a last resort haha. Not going so well either, but at least getting a render out between crashes.

Hi,
everything seems to work as expected here with Instance Color and X-Particles, in c4doctane 2022.1.2-R4: Please try with this example scene and report back, thanks: ciao,
Beppe

So it seems my/Octane's issue is a VERY specific one.

In the process of setting up a dummy scene, I realized, as bepeg4d just pointed out, that the Instance Color node was indeed working with XParticles.
The problem only showed up when I decided to emit from a vertex map like I was in my original scene....initially, this worked in my test.

However, it was only when I used a vertex map generated by xparticles using the "Vertex Map Source" utility did the problem show up again. This creates a vertex map tag on the object called VMSource.
I can delete the Vertex Map Source utility after the map is created, and the map remains, but it STILL brings octane/c4d to its knees. However, emitting from a regular vertex map created with fields works fine. This is annoying, but not detrimental to my project, as I will just created the vertex map another way.

Hopefully this helps someone else in a similar boat, and it would be great if the next Octane update had a fix for it.

Please make a simple scene without NDA and send it us