Hello,
I have started to use models with VisitSubTree cores recently. Now I
have discovered the following odd behavior that I can't explain:
Case 1: Simple graph ending in a VisitSubTree-Node which points to a sub
tree. The sub tree is managed in a container collection which is
attached to the VisitSubTree node.
Case 2: Additionally to case 1 I add a loaded dino model to the scene
manager.
Trafo
+
|
MaterialChunkOverrideGroup
+
|
VisitSubTree*--->ContainerCollection
| +
| |
v |
SubTree<----------------
Result: Case 2 is rendered fine; I see the dino and the sub tree
geometry. Case 1 does not show the sub tree geometry.
Can anyone explain that?
Is there anything missing in my setup?
I did choose this setup because I have to render SubTree very often. In
order to provide persistence I came up with the ContainerCollection.
SubTree is only inserted to VisitSubTrees.
Best,
Johannes
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
