Pretty much. Here’s an example of one approach: https://hongbofu.people.ust.hk/doc/bilateral_normal_filtering_tvcg11.pdf
Hi guys,
I just tested out your plugin and I have to say it’s very interesting so thank you Daniel for your work.
Here is an example of the research I did last week, performing multiple difference booleans using 660 spheres.
I still have one question in mind : why the size of the box input in the isomesh 2 component affects the resolution of the mesh ? In my case, I noticed that the higher the reference box is, the faster the isomesh 2 component works. Or maybe I’m missing something?
I’ll post a file later if needed.
I think it would be really convenient if the components of Isopod could provide a low-poly mesh preview at every step, not just during the final meshing process. Modeling is an iterative optimization process—the easier it is to confirm the result of the previous step, the more convenient it becomes to refine the next.
The ‘resolution’ input is the number of divisions along the shortest side of the box.
So using a larger box with the same resolution means larger cells, so your object will occupy fewer cells and therefore have fewer faces and be quicker to mesh.
I agree that working at lower resolution while developing a design then switching to higher resolution for the final meshing is convenient, and this is also the way I usually work.
Do you have something else in mind beyond simply changing the resolution values like this?
It can also sometimes be useful to mesh only a small region of the object at higher resolution during development (because for thin features a coarse preview mesh might not be able to capture the details well enough), then switch to the full object at the end.
@Quan_Li exploration using Field texture is very fast and quite easy to use. And it has the big advantage to represent the inside that is very hard to see with a mesh and a porous structure.
I hope every component in Isopod provides mesh preview in low poly by default (or under some conditions). To confirm where I am, I must countlessly repeat the checking behavior by wiring the current component to one of the meshing components. I hope Isopod can spare users this inconvenience.
You can create a cluster or snippet with two inputs and a gate. I have something similar for a mesh pipe component where most times a coarse result is desired but for export I can change a value list which contains all the relevant values…
I hope not…
Isn’t it good to see what you’re doing while you’re doing it?
Realtime preview… ok that would be nice…
Just maybe not by default and it needs to be possible to enable / disable without having to right click into the component
Awesome plugin Daniel - good fun ! Having access to the uncomplied C# version makes it a lot easier to extend it.
Here’s an extended TPMS component with roughly 40 surface definitions build in.
TPMS isopod samples.gh (25.4 KB)
For good measure here are components for for polar and spherical mapping:
Polar field modifier.gh (29.4 KB)
Spherical field modifier.gh (30.2 KB)
Nice! Thanks for sharing.