The real problem is the huge number of nodes in the scenegraph. When you open the file and display these little red indicators and then open the Scene inspector utility you'll see that one view provider has a sub-graph with thousands of elements. So, the bottleneck is to traverse these many nodes for every little pan or rotate action. IMO, it should be first checked if the rendering time can be speed up by re-organizing the scene graph.Without this commit it's a ten minute hang
With it, it's sluggish performance.
I'm talking about manipulating the 3d view (rotate, pan,etc.)
wrong return nodes in getNodesByEdge
Moderator: bernd
Forum rules
and Helpful information for the FEM forum
and Helpful information for the FEM forum
Re: wrong return nodes in getNodesByEdge
Re: wrong return nodes in getNodesByEdge
What do you mean by reorganizing the szene graph? Would it not better just to make less arrows by making a bigger step between the arrows. viewtopic.php?f=18&t=9884wmayer wrote:The real problem is the huge number of nodes in the scenegraph. When you open the file and display these little red indicators and then open the Scene inspector utility you'll see that one view provider has a sub-graph with thousands of elements. So, the bottleneck is to traverse these many nodes for every little pan or rotate action. IMO, it should be first checked if the rendering time can be speed up by re-organizing the scene graph.
Re: wrong return nodes in getNodesByEdge
1. It could be checked if using SoGroup instead of SoSeparator speeds it upWhat do you mean by reorganizing the szene graph?
2. It could be checked if for every little indicator a new sub-graph is created or if only one instance is created with a different translation node
3. It could be checked if using SoMultipleCopy node can be used
4. It could be checked if display lists or other OpenGL tricks can be applied
This cures the symptoms but it doesn't really fix the problem. But sure, this can be done additionally.Would it not better just to make less arrows by making a bigger step between the arrows. viewtopic.php?f=18&t=9884
Btw, recently you were talking about fixing some issues in the Abaqus writer. Do you remember in which thread?
Re: wrong return nodes in getNodesByEdge
Got it, thanks Werner.
viewtopic.php?f=18&t=10110&start=10#p83382wmayer wrote:Btw, recently you were talking about fixing some issues in the Abaqus writer. Do you remember in which thread?