Skip to content
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

fix #5118 Dual Mesh Node Extended Algorithm #5119

Merged
merged 19 commits into from
May 25, 2024

Conversation

satabol
Copy link
Collaborator

@satabol satabol commented May 5, 2024

fix #5118

  • move DualMesh to old_nodes/dual_mesh.py
  • create SvDualMeshNodeMK2

test file:
Issue.DualMesh.Tests.003.blend.zip

Examples in test file:

image

fix #5118
- move DualMesh to old_nodes/dual_mesh.py
- create SvDualMeshNodeMK2
@satabol
Copy link
Collaborator Author

satabol commented May 6, 2024

image

@satabol
Copy link
Collaborator Author

satabol commented May 6, 2024

Added new input socket "Levels":
DualMesh levels 001

If source object has faces with different normals:
DualMesh levels 002

@satabol
Copy link
Collaborator Author

satabol commented May 6, 2024

Second Level Issue:
image

This is not a glitch:
image

So... Dual Mesh is not like subdiv! You can gen non-manifold geometry after Dual Mesh.

- fix tests to use new node (Architecture/Curved_Hexagonal_Truss.json). No change schema
- fix buld errors in console for node "generators_extended/polygon_grid.py"
- add a few performance to dual_mesh by clean bmesh not recreate.
@satabol
Copy link
Collaborator Author

satabol commented May 8, 2024

Images for comments in code

image
image
image
image
image
image
image
image

for face in bm.faces:
new_verts[face.index] = face.calc_center_median()
def dual_mesh(bm, recalc_normals=True, keep_boundaries=False):
from time import time_ns
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it still needed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For a little time

# vert.link_edges (or faces in vert.link_faces)
# is undefined, so we have to sort them somehow.
# some definitions:
# 1. source vertices, edges, faces - elements of cource mesh. Some vertices, edges and faces may be as single.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

*source.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@satabol satabol force-pushed the fix_5118_Dual_Mesh_Node_Extended_Algorithm branch from bbc9e38 to c0bf980 Compare May 25, 2024 19:36
# Conflicts:
#	index.yaml
#	menus/full_by_data_type.yaml
#	menus/full_nortikin.yaml
@satabol satabol merged commit 2761632 into master May 25, 2024
2 checks passed
@satabol satabol deleted the fix_5118_Dual_Mesh_Node_Extended_Algorithm branch May 25, 2024 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dual Mesh Node Extended Algorithm
2 participants