srek

Just creating a new UV tag doe snot help. There are numerous tutorials on UV mapping in Cinema 4D available. In the most simple case you can try to use one of the standard projections in the material tag instead of UV.

Most geometry scene nodes come with selection options. By default they use either the currently selected elements (default in the selection string), or if none are selected all. If you want to use the elements marked by a selection tag you need to enter the name of the selection in quotation marks. If you want them to only work if there are selected elements use active instead of default.

Like Chester wrote, this is just a couple of nodes more to define the condition than you might be comfortable with, but structurally it’s the same.

I am not sure i understand the problem. You usually solve this in two steps, first is to determine the condition, that can be a simple comparison, be it <,>,<=,==,>=,<> or anything you need to cobble together with multiple nodes, and in the second step you react on the result using the Condition node. You can stagger multiple condition nodes if needed as well.

In Scene Nodes it is only called Switch now and yes, it is the direct equivalent to Switch/Case, though it does not have a default

Due to the quivalence of True=1 and False=0 you can actually do more complex setups to determine the selected branch

In a node sytem like scene nodes or xpresso you create a branch for each result, then use a switch node to choose one based on the condition you define.

If you are in R25 (you don't have your version set up in your profile), you can simply drop a Transform Element Capsule under your object, switch it to Edge mode and enter "active" in the selection string. Then adjust the Transform-S value to scale the selected edges to your liking.

Data Analytics are a much wider field than just application feedback/telemetry, which Cinema now has for i think it might nearly be 10 years or so. Data Analytics in regards to the application itself is pretty much straight forward and doesn't need much of an analyst.

What you can do is i.e. use textures/shaders that can be applied to branches, then make sure you create matching UVs for these when building the tree geometry. You could even use a couple of variations and let them be applied randomly. I can see various solutions for your problem, but none that "just works" without either human interaction or a very well trained neural network.

Ups 🙂

Kitbashing setups are definitely something you can do nicely with Scene Nodes. It is actually something i use right now for personal projects, in this case a very much real world application. I use CInema 4D to model 3D printable tool holders for my workshop, to easily produce variations for different tools i created a simple new geometry primitive that allows me to parametrically adjust the cut out holes for various tools. Setting this up was a thing of a very few minutes and it saves a lot of time after that. During testing Scene Nodes i created multiple setups to parametrically create Furniture, Walls, simple houses, Windows, ... None of those good enough to share as feature useable items, but all meant to make sure that Kitbashing is not only possible, but powerful.

Those would be questions for our SDK team, they are beyond my scope definitely.

In Scene Nodes this is taken care of by the modeling nodes. All attributes attached to geometry like weights, UVs etc. are modified in the best possible way, in most cases interpolation or cloning of attributes, depending on situation and function. This of course only works with the standard types of properties that you can use in geometries. If you create an own structure for this it is up to you to maintain it. This is mostly due to the scene nodes using the exact same modeling functions that users can apply interactively, there is a shared modeling kernel that takes care of this.

Scene nodes in general are multithreaded, but it depends on your exact setup to what degree. Especially modeling operations can often not be fully multithreaded and recursions as well.

There is the active selection workflow which resembels what you describe. It effectively mimicks interactive modeling. The alternatives are either named selections, like in my example, or explicit selection before each operation either via selection nodes/capsules or directly entering indices. Scene Nodes and Capsules are pretty flexible here and all these workflows can be mixed and matched if you want.

Newly Created has no object manager equivalent since it would need two different geometries to compare. However you can simply intitially store all polygons in a selection and then use first inset, then extrude with that selection.Capsule Inset Extrude 01.c4d This would be the Scene Nodes setup

Newly Created has no object manager equivalent since it would need two different geometries to compare. However you can simply intitially store all polygons in a selection and then use first inset, then extrude with that selection.Capsule Inset Extrude 01.c4d

That also helps if you were to use scene motion blur or change the frame rate.

You are absolutely right, i made a serious mistake in the setup by manipulating the position, i was somehow stuck in TP mindset and thought about adding to velocity.

The userdata value is the added velocity per second. Acceleration is defined as change of speed over time, so yes, the Userdata value is acceleration 😉

In the attached scene you can see how to control the position by using an animated acceleration value (Userdata). Due to a check for difference in scene time this setup will not change the position on a simple refresh. Xpresso Acceleration_0001.c4d

That is actually a long standing issue with some TP parameters. You can work around this by adjusting the value of the keyframe(s) in the timeline.

I like the idea, though i fear i can't contribute much over all i would like to kick it off with this Antiprism setup Any D>=3 is supported, the setup does not generate UVs. Antiprism.c4d