Open alxbilger opened 3 years ago
Not really related to your issue itself (GUI) but are you sure that DefaultCollisionGroupManager
is working well? last time I tried, if you let the simulation running, you can see in MechanicalObjects
keeping allocating vectors (without deleting them)... leading to a big slowdown and memory consumption.
No I am not sure. And I strongly suspect that it is related to the crash revealed in #2047. If what you say is true, it is a critical bug: I count 156 scenes (.scn) in Sofa where there is a DefaultCollisionGroupManager
As a workaround, the Qt tree view can be refreshed by switching to another tab (for example 'View'), and going back into the 'Graph' tab.
The component
DefaultCollisionGroupManager
manipulates the scene graph structure, by creating nodes, and moving nodes or objects. It happens when there are contacts. The scene graph is correctly updated, but the tree in the runSofa Qt panel is not correctly updated according to the new graph structure. Here is an example: In the screenshot, we can see that the root node has only one child node in the Qt panel (SaladBowl
), but it has two child nodes in its Datachild
(SaladBowl
andcollision1
).collision1
is created byDefaultCollisionGroupManager
after a contact and should contain other nodes and objects. The issue arises inexamples/Tutorials/Collision/MultipleObjectsDynamicCollisionGroups.scn
where I took the screenshot, but also in other scenes with aDefaultCollisionGroupManager
.Note:
DefaultCollisionGroupManager
is optional in a scene.