Feat (Group): Send meshes separately under the group #104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oguzhankoral
added
bug
Closed
oguzhankoral
force-pushed
the
oguzhan/refactor-group-meshes
branch
from
2a8283c
to
6ccb03c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Group entities send to Speckle separately instead of grouping them according to material. Otherwise we have to deal with similar problem on self-intersected faces. Which there are no ideal solution yet.
Additionaly scoped face cleanup (merge coplanars) implemented. previously it was merging regardlessly they are under the same scope or not. When we receive previously split faces as below, we can receive them as is.