Awesome tutorial man! I've been using the boolean modifier since day one and didn't know the function of some of the operations... heck, I've been using booleans even before the modifier 😅
Great intro to the new Boolean mod. I've loved ProBooleans for years. This is even better. Very useful demo. Would love to see more tutes on 2024/5 features.
awesome content! thank you so much! It is very powerfull method... wonder if ADSK is thinking on implementing also Prism... as it is GPU accelerated and much faster.
Would be great to have the "Bake" modifier, or option in boolean which cached state of parameters, so it will increase performance if we no need temporary to change something in boolean parameters. Hope you understand what I mean.
It is case by case. For example, if you move anything in the middle, all the above operands need to be re-evaulated. If you move the last one, it should be better.
@@changsooeun ok, try that. Take a box, put an array modifier on top(count 5 on x,y,z), put a boolean modifier on top. Make a new box and subtract the new box with the boolean. Animate the box. I get 6 FPS with my new workstation and a new gpu. I am no blender user, but i made a test in blender and got 25 fps. Why is boolean slow in max?
@@JP3D81 I just tried on my pc. I got 20fps. Also, max boolean has a lot of mesh clean up code to provide a stable and predictable result which cost processing time. Also, it is based on mnmesh2, and it is still evolving. So, the performance will be improved more in the future.
I've been using 3ds Max since 2003, so I know what I'm talking about. From what I see, you're trying to convince people that 3ds Max can be used as a procedural tool. But that's not the reality. It will crash, lag, and struggle to keep up, and you'll end up having to collapse everything just to get your work done. Go fix the bugs reported by users since 2015 that still haven't been addressed, instead of wasting our time every year with Chamfer and Boolean modifier improvements
