Havealot

You can add a Vertex Color tag to the connect and drag in the Cloner as a MoGraph Field Layer. It's not the most efficient way and it only works if the matrix of each clone also happens to be the the closest clone matrix for each mesh point. But if your clones are not overlapping and a bit separated, then this can work without baking.

It is true that you can't drive the creation of particles with map, shader or noise yet. But there are two workarounds. You can either drive a polygon selection with map/shaders/noise and use that to restrict the emission, or you can emit evenly and instantly kill particles based on a map/shader/noise. Here is an example. The shader field drives a vertex color tag which is then used to set the particle colors on emission. Particles are emitted into a first group where there color is checked. If the it is below a certain value the particle is killed right away, if not it is moved to a permanent group where it will happily continue it's particle life. In case you wondering where the animation is coming from, that's set in the Shader Field with the remapping graph to cycle through different grey values of the texture. This is not the most efficient way as the buffers need to be cleaned up more frequently than needed, but you can achieve the intended effect. kill_by_map.c4d

Try implementing it. And make sure it runs on CPU, GPU (not just on NVIDIA), ARM processors, all operating system, correctly deals with ACEs,...

That can be done with a shader field in the vertex color tag. No need for Scene Nodes. But: You can do some cool scene node setups when it comes to scattering initial spawn locations for the particles and crafting your own velocities and such.

That's fair. Autodesk just released Maya and Max 2025 in March 2024 😄

@Johnny Maunason For this particular use case the Fracture object isn't the right solution. Just group your objects along with the effector (with deformation set to object) under a null and it should scale relative to the individual axes.

@Jaee Is your setup correct? I assume what you are trying to do is to use the simluted (low res) version of a mesh to deform a high res net. But your deformer is a child of the wrong object.

Looks like there is an issue with the triangle mesh option in the collider tag. Use convex hull or box. And if you can try to keep the "thickness" higher. It is used in the collision calculation and larger values make it more robust. Between rigid body objects this won't lead to a gap. In only adds to the gaps between rigid body objects and collider objects. And: Avoid initial setups with intersections of collision shapes. If you have a stack of stuff with all objects sitting flush on top of each other and the bottom one intersects with the floor collider, the fist execution will have a collision resolution that propagates through the whole stack. You can start we a relaxed state with a bit of a gap and let them fall into the stack via the simulation. Once they have come to a stable rest you can set that as the new initial state for the simulation.

@LLS It is just a loop in which you can update variables in each iteration. In python it would look somthing like this: # Initialize your vectors and array. This is the equivalent of creating the initial ports on the outside of the Loop Carried Value and feeding them with initial values. start = c4d.Vector(1, 2, 3) end = c4d.Vector(4, 5, 6) hit_points = [] # Specify the range for your loop. In Scene Nodes the loop range is defined by the Range Node outside of the Loop Carried Value. In this setup it controls how many bounces are being created. for i in range(10): # This is the inside of the loop where you do your thing and then update your variables based on some logic. This will happen in each iteration. start = end end = start + c4d.Vector(i, i, i) # If you need all of the inbetween results later in the node graph you can store them in an Array by appending them in every iteration. array_of_vectors.append(end) #Now the range / loop is done and we are leaving it's scope. If you access the variables now you'll get the state of the last iteration for start and end and an array of all the iteration states for hit_points. Hope that helps.

@HappyPolygon That is GLSL. I have managed porting a shader from GLSL to OSL in the past. But I am not sure if this one will work.

@LLS One benefit you'd get in Houdini for this type of scenario would be direct support of volumes. Scene Nodes doesn't have volume nodes so you'll have work with a combination of classic C4D and Scene Nodes. Regarding multi instance: Of course Houdini has instancing. Regarding volume builder: I've never done any direct comparisons but I would assume it is pretty much the same. In many cases Houdini isn't much faster than other tools. But since there is automatic caching and a nice workflow to work with disk caches you often get better perceived performance over all.

Who is Bob?

@hyyde This was just meant as a workaround. It's a known issue and will be fixed in the next release. Please still try if using default layouts gets rid of the crashes on your end. And unless you haven't done so, please also send reports for crashes that occur without plugins.

@hyyde There is an issue related to the use of custom layouts. Are you using any of those? If it's an option in your case, maybe you can use the standard layouts until a fix is released.

@3D-Pangel Maybe try using TP instead.