srek

No one will be able to tell you anything useful without seeing the scene. With Scene Nodes it can easily happen that an error made with iterations will result in enormous amounts of data and processing. Share the file and we might get an idea what is happening.

Not this specific setup since this applies the exact same function to all UV points. However if you process all UV points separately and reposition them according to a projection of the related geometry point position you can create your very own UV projections. It is a good deal more complex than this example though.

This would be a setup to modify every UV position using a matrix. You can translate, rotate and scale

Thanks, i wasn't aware of this option to use line cut. I reported the issue concerning numerical precission.

I think they are actually non planar, they are folded 180°.

I might see what you mean. If you do multiple line cuts one after the other with overlapping lines it can happen that the resulting polygons are partly inverted, which is shown as non planar in the mesh checker. While this should of course not happen ideally, it would be more an issue of bad practice. You should not do overlapping cuts in a single modeling operation.

If you cut a planar polygon the resulting polygons should each be planar as well, within numerical precision. If you have an example where this is not the case i am interested.

Sorry, but i think you interpreted some things rather freely there. I don’t think Xpresso was ever mentioned as going to be deprecated. There were multiple scenarios on how things could develop depending on a lot of technical issues. That is one reason why scene nodes were referred to as a tech demo and not a feature. Quite a few people tended to overlook this and were then surprised when there was no quick switch over to pure nodes or something like that. Capsules are solidly based on scene nodes, there was never a moment when capsules were a thing and scene nodes weren’t, maybe in someones perception, i don’t know. People tend to bring Xpresso into the scene nodes discussion, i think mostly because they are also nodes, but that is the only thing they have in common. The difference shouldn’t be to hard to understand for someone who knows Cinema 4D and is aware of the differences between expressions and objects.

The key issue is that to be able to make them work in the same context would require a complete rebuild of the object system, which would invalidate every existing scene and would change a lot of functionality. So it is not only a lot of work, but also a tremendous risk.

If it were possible to do this in an in any way reasonable way, we would do it. It sounds straightforward but is anything but.

I wrote something on that https://nodebase.info/general/scene-nodes-vs-xpresso/

.max is a parametric file format, it requires 3DS max to be installed for any kind of conversion.

Everything in the Prefs can be deleted without major issues, in most cases it will just be replaced with the defaults on the next start.

I actually drive a Smart 😉

Hopefully in the same state as now, up and running.

I would be surprised if that happens any time soon. Scene Nodes are still developing rapidly and you simply can't produce a book fast enough for it not to be at least partially outdated on release. It would near obsolete within to short a time to make this an economically viable effort.

🙂 It's really only this you need to look at

I'll see what i can come up with, but you can already find an example on this if you take a look into the Noise Selection node. It uses multiple Switch nodes to choose between different branches, including handling of optionally storing selections.

@HappyPolygoni double checked and Store Selection for Noise Selection does work for me in 2024.0.2. The display of the related tag in the OM seems to be a bit hit and miss, but the stored selection does work.

The selection shown on Store Selection is actually the Selection port of the node, it being shown in the Attribute Manager is an oversight. Store Selection on Noise Selection should work, I’ll check if it is a bug.

Please try the latest version. This doesn't happen for me in 2024.0.2

You don't need a special node, just unfold the Op port

One more for those who want to start building their own geometry modifiers https://nodebase.info/example/using-loops-for-modeling/

What Hrvoje said. You can think of the Loop Carried Value node as the body of the looping function. If you want to run it multiple times just set the controlling iterator accordingly.

Both doable, i have an outline laying around here, maybe i do that. The Random Walk is something that isn't hard to do technically, but making it an artist friendly tool is a bit more challenging. Thanks for the suggestions