-
Notifications
You must be signed in to change notification settings - Fork 4
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
HYDRA-600 : Add filtering scene index interface to flow viewport tool… #21
Conversation
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.
Mostly minor comments. My main concern is the visibility support that is attached to nodes. I understand the idea, but I wonder if all the design and workflow implications are there:
- It only supports Maya nodes. I wonder if using UFE services would have allowed us to support LookDevX or USD nodes as well.
- It seems to only consider the Dag node visibility attribute. However, since Dag nodes have inherited visibility (from their ancestors), visibility must be computed, and cannot be read from a single attribute.
- It doesn't consider other factors that influence visibility, such as isolate select and display layers.
- I wonder if we should also consider Maya DG (Dataflow Graph) nodes. They aren't in the 3D scene, and therefore don't have visibility, but they may be better suited for rendering control such as providing scene index parameters.
To be discussed.
...PI/perViewportSceneIndicesData/fvpViewportInformationAndSceneIndicesPerViewportDataManager.h
Outdated
Show resolved
Hide resolved
test/lib/mayaUsd/render/mayaToHydra/cpp/testFlowViewportAPIFilterPrims.cpp
Outdated
Show resolved
Hide resolved
test/lib/mayaUsd/render/mayaToHydra/cpp/testFlowViewportAPIFilterPrims.cpp
Outdated
Show resolved
Hide resolved
lib/flowViewport/API/perViewportSceneIndicesData/fvpFilteringSceneIndicesChainManager.h
Outdated
Show resolved
Hide resolved
lib/flowViewport/API/perViewportSceneIndicesData/fvpFilteringSceneIndexDataAbstractFactory.h
Show resolved
Hide resolved
lib/flowViewport/API/perViewportSceneIndicesData/fvpFilteringSceneIndicesChainManager.cpp
Outdated
Show resolved
Hide resolved
lib/flowViewport/API/perViewportSceneIndicesData/fvpFilteringSceneIndicesChainManager.cpp
Outdated
Show resolved
Hide resolved
lib/flowViewport/API/perViewportSceneIndicesData/fvpFilteringSceneIndexDataBase.h
Outdated
Show resolved
Hide resolved
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.
We'll go with your suggestion to use a vector for
viewportInformationAndSceneIndicesPerViewportDataSet
Should be done after that!
lib/mayaHydra/hydraExtensions/sceneIndex/mayaHydraMayaFilteringSceneIndexData.cpp
Show resolved
Hide resolved
lib/mayaHydra/hydraExtensions/sceneIndex/mayaHydraMayaFilteringSceneIndexData.cpp
Show resolved
Hide resolved
lib/flowViewport/API/perViewportSceneIndicesData/fvpFilteringSceneIndexDataAbstractFactory.h
Show resolved
Hide resolved
lib/flowViewport/API/perViewportSceneIndicesData/fvpFilteringSceneIndicesChainManager.cpp
Outdated
Show resolved
Hide resolved
…nAndSceneIndicesPerViewportData and add const where it was possible.
…kit.