Hrvoje

Depends what you do. If you are rendering a lot then gpu performance is more important. Regarding motherboards, it is pretty much all the same except for people that are enthusiastic about that - same factory, different brand logo 🙂. If you are into silent environment then check aftermarket cooling, such as Noctua. Also, this can help https://dropandrender.com/cinebench-benchmarks/

All nodes capsules, both nodes mesh and spline, selection and geometry modifiers can now easily ingest input objects. Objects can be ingested into graph as a child or link. object. Additionaly, whole linear hierarchies can be imported via object children and object links. For example, you can now subordinate some objects under nodes mesh and use them as input in robust way. The principle is the same as you would put a mesh under subdivision generator, spline under sweep or some objects under volume generator, child objects are simply available for processing. In case of a link, think link slot which cloner has when set to object mode, target for constrains or similar. In case of links, think list of effectors or fields. Here is how you add them to Capsuies Once the capsule is processing the input it will change color to generator color to indicate that In case of link or links it is the same as in rest of C4D This eases up referencing and ingesting objects to great extent, absolutely love it 🙂

Here is a setup which showos how to do particle to particle collision. Although there is no real collisions available at this moment, some modifiers can be adjusted to do a very convincing job 🙂 Bubbles.c4d

Love Noseman, he is even more fun in person 🙂 Personally, I am the happiest with proper object inputs for capsules, that is a big feature for me

Known issue, unfortunately that is the way collision deformer was created back then. You could fake it by creating 6 hidden collision cubes around the sphere to get the collisions you are after, or take a look at this nodes rig https://www.youtube.com/watch?v=TR3h6msfiyQ&t=668s

Took a quick look, but it is clear that joint structure is not the same. You will need to export from Cascadeur app (never used it) C4D compatible structure. Their website says that support C4D, so look at the docs 🙂

I see what you mean. You will need to create multi stage fracturing. Create a first level of two pieces and apply rigid body to it. Create a MoGraph selection of top part of the head (you will use it for second stage). Create new Fracturing as parent of previous one. Here load the MoGraph selection from previous to restrict breaking only the selected part so you cna have detailed break in your second stage. Apply rigid body tag to top fracturing as well. Now you will need to animate the enabled state of top fracturing, but you should be able to get what you are after. Also, try with bullet dynamics as well, you might get more pelasing result in this particular scenario

Hi Hard to help without a scene file..

@LLS Very nice setup!

Here is some simple trailing, MoInstance like but with nodes. Control the trail count in compare node. The advantage is taht the setup can be greatlu expanded, such as usig mixed objects and similar Simple_Trailing.c4d

@Cerbera Wonderful modelling skills, I applaude! 👏

@DALII Here is how you can split any spline into parts between control points. This makes it easier to process since you will always work on single spline with two points. You can then resample that any way you find useful split_control_points.c4d

You need to build your own resample then. Easiest would be to explode each line between control points to a spline itself. You can then use evaluate spline node and add control points based on any criteria (distance, percentage whatnot).

@DALII So, basically you want to check if resampled point (new point) is more than some value in distance from original point and then simply don't generate it? Or, you want to treat segment between two points individually and resample just that?

Please post the scene here, make sure you strip the scene to bare minimum and describe the issue as best as you cna for easier troubleshooting.

Can you please attach a scene file?

Not at my machine at the moemnt, but if you are using first voronoi just to get two objects, why not use current state to object and have those two pieces as starting point? That would resolve your issue since you would need a single voronoi then? If not, will have to look at the scene...

@zeden I confirmed it myself. Bug is assigned and will be addressed. The issue is not in fact in delete node, rather something else so support was not really capable in this case to determine that on required technical level.

More than welcome to ask as many questions as you want 🙂

Obviously biased here but C4D is quite a package at the moment 🙂 Regarding Modo, abandoning such a large code base must have been difficult decision. There must be a lot of tech that will be extracted and placed elsewhere. There is also a remote possibility, pure speculation of course, to create new3D package.

That looks like a bug : /

Nope. There is no add point on edge (effectively) yet in nodes. you can insert the poing manually then rebuild topology but is not easy with more complex models

Was reading Modo forums, seems that this was cooking for a while now...

Here is a simple slicing a spline : ) 140_Slice_Spline.c4d

There is no bridge as we have it in modelling tools, but there are ways to do simple edge bridging. This revolves mostly around extruding one edge, manipulating the end points and connecting it with connect node.