The new Node Geometry feature!

Announcements
21

Thanks a lot! I didn’t notice this library before. However, it seems that this library is specifically for CAD scenarios that pay attention to manufacturing and architecture. The differences between this library and procedural modeling (in games) are similar to the differences between CAD and Blender, with some similar modeling capabilities but significant differences in functionality and underlying primitives.

Procedural modeling in games is more similar to Houdini SOP and Blender geometry nodes. It’s like you’re modeling in Blender, but instead of using the software interface, you’re using the code for automation. Use code to select points/edges/faces, and extrude, inset, bevel, etc. to manipulate them. This process will enhance efficiency greatly since it can reuse the entire modeling process instead of just the final result

22

Indeed! WebGL limits some GPU capabilities. Look forward to WebGPU bringing a whole new world!

However, using a CPU may sometimes be acceptable. The modeling calculation is supposed to be done during the game loading process or another thread with cache support; the execution time “a little bit longer” may not have a big impact. It looks like Blender is using the CPU for its geometry node, and the performance is okay, even in the real-time interaction scenario.

Houdini seems to use the CPU to implement its SOP as well and only uses OpenCL to accelerate certain operations, AFAIK.