-
-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VoxelTool.do_* functions do not ignore VoxelModifier on terrain #665
Comments
Yes, I'm aware that I'm using different scales (there are reasons why I'm doing this, but it's a bit out of scope for this issue) and why the issue happens. With sdf scale = 1 values are: Thus, My main point with this report, is that, presence of modifier should not affect the result (after all, it's intended to be non-destructive preview of the mesh). |
Unfortunately this cannot be "fixed", the problem is you're expecting that using wrong SDF alongside correct SDF to behave correctly, which can't happen.
|
I should have mentioned in an initial issue, that I expected the sphere on the left to be smooth again, after moving VoxelModifier away as I thought it was applied last. However, now knowing that modifiers are to be treated as part of terrain this behavior is to be expected. So this is not an issue. |
Describe the bug
When trying to edit terrain with VoxelTool, the result depends on whether there was VoxelModifier in the area of edit. Effects of this can be noticed when stamping a shape with higher SDF scale.
To show an example:
stamp_sdf
with VoxelModifierMesh being there.stamp_sdf
without VoxelModifierMesh being there.See image:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
SDF values after an edit should be the same with or without VoxelModifier nodes in the edited area.
Environment
MRP
Test VoxelMeshSDF stamp with VoxelModifierMesh.zip
The text was updated successfully, but these errors were encountered: