Unless there is a definitive enough way to tell apart
offset too bigandclosed meshcases, I think we should just stick to ambiguous warning. Otherwise, we risk misinforming the user.
Agr…
Well, I could not find something very informative in the OpenVDB docs. The only thing I could find is that a closed surface is needed.
So I went for some tests. I added print(levelset.info(5))…
Good catch. I've mostly ignored failure conditions.
The first reason is due to too large an offset. The other reason is when the mesh does not define a closed space. I think those conditions…
With the separator it looks definitely better.
I think the preset is useful because of my points about the default voxel size. If a user has a setup where this default isn't appropriate, having…
I did not understand what you meant by "expand". Now I know, and it looks really better. The separator also helps.
I'm sorry about you being sick. I hope when you will be already fully recovered when you read this.
This time I implemented all suggestions. At least I hope. Last time a wrong default flew by...…
I've committed some code. I've tried to make all the suggested changes, with some exceptions:
- Default voxel size is 1.0
- Offset now is only positive. Direction is indicated by a new boolean…
I'm actually pretty comfortable around matrices. I had a good training in linear algebra, and I've been using NumPy way longer than Blender.
I was looking for something like `obj_hollow.matrix_wo…
This is cool! I did not know about it. I much prefer the dialog, as the operator UI can then be just a button.
Duplication of the operator settings is a pattern that occur often in the 3D-Print…
I'm back.
Regarding offset sign, I would rather go with an unsigned thickness parameter and a direction switch toggle, instead of just flipping the sign. I think it would be easier for users to…