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.
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
DYN-3896 Add support for geometry instancing in render pipeline #11914
DYN-3896 Add support for geometry instancing in render pipeline #11914
Changes from all commits
987381f
0824814
37ceb00
3aecdc4
3276e67
ca899f7
0de95b0
f901cb6
774d66e
c69a6cc
c379ed4
c2f34d2
6a08c8a
a95a881
628392b
0a5b8f3
a0302cd
e7170fe
f60c9b6
f407a71
60aabb8
a8caa7b
c05c323
0da5120
cfb521c
fec13a9
e38a40b
af38da1
1850bc0
df92121
2c9551f
52331e1
b4b2fe7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mjkkirschner Hmmmmm.... Not sure but we may need to handle a transform that has both mesh and line type tessellation data. Maybe when edges are on. I can't remember how that case was supported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be a bit of a hack but the LIbG portion could actually handle this ^^^ I think. I always wondered why we didn't handle the
ShowEdges
in the base tessellation call. Maybe puts too much ownership on those implementing IGraphicItem. In this case we are still internal so it may work to let the instanceableItem handle the data. In the case of a cube,AddBaseTessellation(instancingPackage, factory.TessellationParameters)
could inspect theTessellationParameters
and add only a mesh or a mesh and line data if edges are needed. They would have to have separate GUIDs. The subsequent call toAddInstance(instancingPackage, factory.TessellationParameters, labelKey)
could also add the correct instance references fo either mesh only or mesh and line data.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may also be follow up task?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we can just push the line data to the baseTessellation from this method:
Dynamo/src/DynamoCore/Scheduler/UpdateRenderPackageAsyncTask.cs
Line 262 in 9740b24
or always generate the edge data in baseTessellation but only using it (extracting it from the render package) if show edges is on.
For the current state of the PR, I think we need to decide the following:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could be also...
4. Edges added within instancing implementation.