for fracturing and rigid bodies, tyflow is way way faster. Tyflow is like a cheat code, to do things very fast since you have a lot of "blocks" prebuild, where in houdini you need to build everything from scratch ( and some of the higuer SOP leves they build are quite bad). But the good thing of houdini is how the data flow no matter what, and how you can build very complex things (with time). The downside of tyflow, is that something is not build in... its difficult to build it yourself, and that you can not go very deep in to manipulating data low level, you are constrained in what its already there.

Ahora hace 4 meses que dejé scanline, pero aun así me temo que es imposible, es software no comercial y son muy reticentes de mostrar nada.

@@andvfx una verdadera lastima.

@@andvfx algo que puedas compartir? aun corre dentro de max? o ya es una aplicacion aparte?

@@juanromero-fi2cf Lo siento, no puedo compartir ningun tipo de informacion al respeto.

@@ermperson I will bet money that A: you will run into failed booleans at some point in houdini, and B: tyflow its 100 times faster. As you get in to more complex assets the difference between the two systems are bigger and bigger.

@@andvfx As for the bad grid, I admit the possibility that Boolean is better in tflow than in Houdini. I did it in 10 minutes, the simulation is realtime and I can easily bypass moments with bad work of the Boolean. But I have doubts that in all cases Sergey's Boolean worked perfectly. I can throw off my hip scene, you can try to watch, compare if you have a setup from the video.

@ sure! But on my past company I spent a good 2 weeks comparing houdini booleans vs tyflow booleans, and the difference is huge. Sure you can do anything in houdini. But with a lot of mesh prep to dont get into errors, failed booleans or open edges. In tyflow it just works no matter how bad are the nesh or booleans. And being that much faster is a huge difference

@@andvfxI left 1 substep, but it can be easily increased. If during experiments there are problems with geometry, I left several disabled nodes that you can play with and that can potentially fix problems with normals or the disappearance of the inner part. H20.5 drive.google.com/file/d/1ioTsEyGJQ6EralFPN7MHGnaQVN57NYC7/view?usp=sharing

Yeah.. another update-nothing xD

​@@tedeusz833ds Max is already powerful but anything new is always welcomed.

@@tedeusz83 3ds Max is already powerful anything new is always welcomed !

@@tedeusz83 What would you like to see in version 2026? 🤔

Why they call it 2026, why not 2025? Never got it?

@@teratronwrx1 thanks! Happy new year!

@@julienchiari thanks! Have a great holidays you too!

Maybe Are not in the edit, but some viewport controls where clearly max.

These features are great compared to other software! Ridiculous complainant, if you can't adapt, it's your own problem, please leave

@@LanCST what features? Most of this stuff is about V-ray or plugins, the software itself is still the same lazy old mess, and dont tell me what to do, who do you think you are? Autodesk is beyond lazy and 3ds Max is outdated by decades, even compared to Maya, and both are gonna get their butts kicked by Blender, C4D and Houdini

@@wallacesousuke1433 3dsmax is a platform, and the plugins are all part of Max, so what you said is not correct. There is no hope to change your mind, just don't mislead others. Max's UI, hotkeys, and so on are much better than other software, and they cannot be imitated

@@LanCST I don't know about other parts, but the shortcuts are a mess. They are completely unpredictable, so it's best to just assign new shortcuts.

​@@공개미-w4l I'm not entirely sure what you mean, but customizing the hotkey max gives enough freedom to change it, which goes beyond bl, houdini, maya