Edit History

There are some very interesting new features. Particles have an extensive list of new functionalities from which the following stand out. The Field-driven density distribution of particles is highly appreciated along with in-built noise shaders for both distribution and emission. Density control shaders and Fields is something I've been asking for MoGraph for years. Finally it can be achieved through particles. Noise Sampling for Color and Data Mapper https://help.maxon.net/c4d/en-us/Content/Resources/Images/2025-2_Particles_NoiseSampling_01.mp4 https://help.maxon.net/c4d/en-us/Content/Resources/Images/2025-2_Particles_NoiseSampling_02.mp4 Neighbor Search algorithm for Flock, Predator Prey and Blending Similar to the geometry density coloring effect I've been asking. Some Scene Node Capsules are now directly available with other primitives from drop-down menus. This was something I was actively arguing about from early versions of Scene Nodes as it was a closely UX-related issue. Things were pointing to parallel ecosystems of the same tools being developed under the same application or tools that were not that easily accessible that would inevitably lead to confusion or frustration among new and old users. It wasn't too long ago you could finally make capsules accessible from custom pallets but that required from users to know how to do that and as SceneNodes was so actively characterized as experimental or system for advanced users, people would prefer staying away from it missing some key features that were not that hard to use after all. Personally I extend my custom Layout with capsules supported by the OM every new version. Now the Line Spline is available along with the Break Spline, Branch Spline (which is an easier MoSpline Turtle), Catenary Spline, Dash Spline, Electric Spline, Partition and Pulse Spline. What I don't know is if they re-developed those tools in C++ or if they are just links to the node implementation with modernized icons to fit with the rest of UI. Well, there are still some argument about what should be characterized as a Generator what as a Modifier and what as a Deformer... For example the Branch Spline is more fitted to the Generators club as it does create additional splines on top of the original but I guess they run out of ideas on how to represent it with a new icon to avoid confusion with the MoSpline... Which leads to other old arrangement arguments like why don't we just have new features part of older tools as modes... For example the Branch Spline as Mode of the MoSpline... Break, Dash, Partition and Pulse modes of a single spline deformer/modifier or Wrap, Shrink Wrap and Spherify as modes of a single deformer... Looking forward to seeing all distribution nodes as modes in the Cloner and Blue Noise as a mode of the Push Apart Effector. New mode for the Look at Camera expression I always thought this to be an old remnant from earlier C4D versions... I never used it because I achieved the exact same effect using the Target tag... I still don't know what the difference between them is... Some unfortunate translation issues: Weird title, not available in English https://help.maxon.net/c4d/en-us/Default.htm#html/OFPBLEND-FP_BLEND_OBJECT_OUTPUT.html Things that we saw in the teaser video but they are not documented (yet) Weave Spline Generator (also expected a better icon for that, here's mine ) Constellation Generator (Plexus effect) Liquid Simulator (yeah... the thing that should be teased the most was not)

interesting release... one thing I noticed right away is why the spline modifiers and generators have the word 'modifier' and 'generator' after them? there is obviously no need for that as we know its a generator and modifier from its icon colour. also just like the 'Spline Wrap' modifier, the word spline should be at the beginning for eg. 'Spline Branch', 'Spline Break' etc etc... this ensures naming consistency with the rest of the modifers/generators as well as conciseness and being DRY(don't repeat yourself)... I feel like there was a lack of attention to detail there before release... and maybe if they plan on adding more spline tools, it might start deserving its own seperate category like the spline shapes...

03/04/2025 Join us for an exciting livestream about the new features in Cinema 4D 2025.2 and Redshift 2025.4 with Elly and Noseman from the Maxon Training Team.

There are, if we look carefully, a number of things subtly wrong with the settings in this scene. As HP predicts above, Render Perfect on the sphere is one of them, and fixes the effect of collision deformer not showing in render if we turn that off. Next we had some suspect settings in the sweep object (parallel movement should be off, Banking should be ON, and End Rotation should be 0 degrees), which fixes the twist in your path spline over the indent, and restores it to correct, contiguous circular form all the way along its length... The mode of the Collision Deformer should be Outside (volume) and the capsule should ideally not be a child of it, though it doesn't particularly matter in this scene. Likewise object order in the OM could be better bearing in mind that Cinema scans downwards through it from the top. Below is more ideal I would say, and general good practice. Next, the curvature in your path spline within the sweep isn't quite matching the curve of the indent in the sphere, resulting in some unevenness in that area. This can be fixed by getting a new path spline for the sweep, which we get by doing Current State to Object on the main sphere (once collided) and then Edge to spline on the centre edge loop of that, but first we have to fix the collision object, which should also ideally be a sphere so that we can choose Hexa type and thereby avoid the complex pole on the end of the capsule it replaces, which was previously confusing the collision deformer, and producing some wanky / uneven collision vertices in the main sphere at the apex of the collision point, which would obviously effect any spline you subsequently derived from it. In my version I wanted a better, higher resolution sphere, but not one that caused the collision deformer any extra work, so changed the type of that sphere to Hexa as well, which then necessitated addition of a Spherify deformer before the Collision Deformer (because hexaspheres are not mathematically spherical out of the gate). And then lastly that went under SDS to give us improved resolution, and my Current State to Object was performed on the SDS instead of the sphere itself, for maximum spline matching. Anyway, I have fixed all that in the scene attached below... groove-on-sphere CBR Fix.c4d CBR