DALII

@Donovan K MXN Thanks for the input. I will definitely watch those videos the next days. 🙂 TBH the last time I've checked Online Resources for Scene Nodes was quite some time ago. But they always were quite general videos where abstract + artsy generators were built. 🙂 But your video looks promising! Thanks. And some update to the Resample you've built: I've tried it to create a guardrail for a window element that is based on a Spline. (Quite a basic example where other things would've been enough too, but I'm currently working on that. 🙂 ) And it works perfect! The guardrail has some even distributed rails, regardless of the Spline length. The only thing I'm seeing now is that sometimes the displayed guardrail appear somewhere in the Scene. (see Screenshot attached) Even though it is rendered correctly. I guess has something to do with the Transform of the Scene Node. It doesn't happen if the Node is on top of the hierarchy + on World Zero. But if I move it into the Window element (to be able to create Instances), it does this thing. If I disable and re-enable it, they disappear until some time later ...) Nothing that would stop me from using it now anyway 🙂 Maybe I'll find the reason after studying the videos.

Wow. The second, advanced Node is exactly what I was looking for. Even spacing between every two-point-pair, the possibility to use it for further operations (like in my test scene, with the Projection onto the ground.) I will try a real use-case tomorrow with some fence or railing. But for now I'm simply happy about that. 🙂 I was trying to get some working setup but no chance, even with the nice help from Hrvoje. Thanks for all the commenting inside the Nodes Setup. I will try to understand it at least a little bit. I mean I get the idea in theory with the Splitting up into sub segments and use the Resample on each of them, but all those nodes that are needed for that ... Phew .. But all of you Node Pros in this thread maybe need to start a YT tutorial series with commentary and step by step explanation for the "Standard Users". 😄

@Hrvoje Each segment between two points individually, but also evenly spaced, based on the 10cm example. But with evenly I mean, it should - at least - look even, even if this means it uses not the 10cm, but 11,5 cm in that specific segment. In my image above, the example on top shows, that the left-most point would be way to close to the original spline point. Now, the Node should "somehow calculate the optimal X value". (I guess my bottom exampel isn't really helpful). Using basic and probably wrong math, I'd say, 34 / 11,33333 should give me 3 points evenly spaced. for that 34 cm segment, with the defined step of 10 cm. There, the additional 1,3333 won't hurt but will keep a nice and tidy looking spline segmentation. Maybe this helps a little bit more. If not, I'm not sure if the idea alone is quite useless anyway 😄

I'm using the Resample Spline node in the Object Manager, simply attaching it as a Child Object to the Spline Object. This works really great most of the time, but sometimes I'd like to have an additional function to the node. Keep the original spline points and use the step, for example 10cm, for resampling, but: Make it a little bit more flexible. The 10cm step can come really close to the original points sometimes, and then an Object Cloner based on that Spline needs some more MoGraph Selection handling to get rid of the unwanted clones. Would it be possible to create a Resample Node, where each Line between two Spline Points is handled individually. It should check, how many 10cm steps are possible, and if it doesn't work out, it should use a little, predefined, Treshold to increase or reduce the Step size a little bit to help the overall look. (in situations where the 10cm don't need to be that precise, of course 🙂 ). I'll provide some images / screenshots later to make it more clear what I'm looking for. For now it seems like it should be possible to make (at least in theory 😄 ) Edit: Now with an image. (hand-drawn, dimensions not that precise) I can't write it down in logical, mathematical terms, but it needs the Treshold value X to be automatically calculated (based on lets say a predefined range that can't be exceeded. In some cases it also could be possible that the best solution would be to remove one clone completely and move the other accordingly). Maybe now it is a little bit more clear 🙂

@Smolak Ah, I see! You have an object 'Wall' where you use Selection Tags to define / assign polygons as 'Windows'. After that, the Node Magic happens. 🙂 Nice approach too. But I guess - until now - not useable with our setup, because we build up walls with a Spline, Extrude Generator for Height and Thickness Generator for, yeah, Thickness. Then, inside the Wall Boole Group, we move around our WindowGRP with built-in Stop Tag. That way we are free to place them where we want without the need of moving Polygons / Vertex inside the Wall object. It should after all keep its non-destructive way. What could be improved would be the handling of thew WindowGRP. Everything merged into one Scene Node would be really great, because then you have centralized Settings and you can even click on the Window object and move it around (instead of re-clicking on the Null object that groups everything together).

Pressing CTRL while selecting a Generator places the object after your selection, on the same hierarchy level. But this doesn't work for everything ... many Nodes objects don't do as they told :). I've created (together with ChatGPT, I believe) a quick + dirty script that moves the first object in the hierarchy to my currently active selection. Maybe something like that?

This looks awesome. Having that much parametric control over even the smallest details, all only with some sliders. Really great! Even though I don't understand how the moveable hole inside the wall is realized. Are these lines you're moving a direct cut into the wall mesh? Or a separate object overlaying the wall object? Really looks great!

These are some great looking windows that you get from a simple plane and ... lets say a few ... nodes :). For our case it still is necessary to have that Cut Out object for the Boole Operator. Because that way we can move that window around freely along the wall mesh and we will always have the hole in the wall aligend to the window asset. Right? Even if the nodes create its own extrusion inside the wall, while rendering the wall wouldn't be opened up and I would need to create a hole in a different way (Directly cutting it out with mesh modification or using a separate Cut Out Object for the Boole) Edit: Sorry, my comment on that somehow includes information regarding my previous discussion. That is because I didn't realize that you're a differnet user. Sorry 😄

If you are not yet familiar with this option, you can also use the arrow keys. Then it works like the system you mentioned for Nuke. Depending on which place between the numbers your cursor is active you can change them more or less precise. 🙂

Thanks! Yes, already thought that this won't work. But I guess it won't work for now? The Stop tag could be somehow reinvented into Nodes. Until then, it will be two objects. Do you mean - for the cleaner setup - I take the cutout polygon object and use XPresso with Bounding Box to resize it accordingly? Or would that be two Node Capsules communication with each other via Capsule Magic and / or Expresso? Thanks for your help and insights! I'm already on setting up at least a window frame scene node where I can adjust the size via Inputs. :))

@Hrvoje Hi! I've a scene attached with the assets that I'm using right now (but without a Scene Nodes recreation for now). Two windows in the ORG folder, one with Stop tag, one without. My desired Scene Node would be a single Object where both of these elements are combined and working with the Wall Boole operator. But I guess this really is something that isn't possible (at least for now?) But even with two Scene Node Assets in the same setup like the polygon objects, I'm way more flexible I guess - time to update the assets :). NodesTestScene_FullWindowAsset.c4d

@Hrvoje Thank you for that tip! Nice that this works the same like the (green) generator that is available in the Object Manager. 🙂 But - and I dont want to be picky or something here 😄 - the problem with the separated boole operation is not solved with the Connect node, right? In my example scene you see, that with the Stop tag, only the Cut Out Object is relevant for the "Wall" Boole Operator. The Window Object simply stays inside the hole without interfering with something. This isn't that special in my test scene, but if there is some more complex window asset inside, it doesn't work out anymore. This would be something for like: Cut Out Object gets into the primary mesh output node and the window asset into some secondary mesh output that isn't that "important" and / or ignored by generators and so on. Don't know ...

@Hrvoje The setup I would want to re-create with a single node would be the one, where I have a cube-like polygon (cut out object) and a window polygon (window asset, originally with a stop tag and both objects are in a boole generator). That way the cut out object makes the hole inside a wall and the window-object stays there without interfering with any boole operation. And now I tried to recreate it with both assets inside a scene node. I can Output the cut out geometry and it does indeed make a hole in the wall like it should. But if I use a second geometry output for the window frame polygon it doesn't show up. And the nodes don't look like there are more options that I can choose from? Your explanation with mindset change and the 'simply don't apply it at first place' sounds nice! And a little bit like it should work if applied correctly. 🙂 I tried to create a basic scene with my original setup and the "approach" to recreate it with Nodes. But quite at the beginning I'm already clueless 😄 NodesTestScene_FullWindow.c4d

@Hrvoje This is awesome! I really don't know how I could not try out such a simple but obvious approach. Maybe the CTRL + Drag is important there? This is exactly how I want my asset to be in the future. 🙂 Only one click to select the whole thing. Really great! Thank you! I'm already on it and trying to get some basic modification of a predefined point selection going but I guess I will check that out for myself for now. Still quite at the beginning with the nodes but at least there is some progress 🙂 . Maybe only one follow up question that will be kinda hard to tackle myself - after some initial searching I'm quite sure it isn't possible right now? Some of our window assets have a bool object integrated and the window polygon object is separated with a Stop tag. Would such a setup be possible inside a scene node? Didn't find anything related with the Shift + C commander and the available Nodes.

@Hrvoje Thanks for your response! We have polygon based window elements like in the screenshot below. For now we have selection tags for differnet parts to modify the size of it. It also contains a separate object for the handle and window sill. (even more stuff with more complex windows) While I know that I can modify the object with nodes applied to the window object itself (manipulating points with selection tags and / or knowing the point ID of the ones i need). But for my best case scenario I would have only a geometry scene node object that contains the window object inside. That would be one single object with a node setup that allows me to manipulate some things. Kind of our own little asset without that nodes attached as a child. I believe that is not possible, right? The next guess was that I need to re-create the window with splines and sweeps / extrudes inside the geometry scene node and that way have only the scene node as my window asset. Hope this is a little bit more clear now 🙂 Sorry!