-
Julien Wintz authored
To be integrated on top on the view layout manager, identifying underlying target to make the view connections for synchronization. So far the example provides a collider to test the physics engine but it has to be changed to control the end of the rope. Colliders will must likely not be used in the case of dtkVisualizationViewer. So far many attributes can be tweaked, however default values have been empirically chosen to decrease CPU usage and increase visual feedback. These are: - Rope vertices count - Rope vertices interaval (or distance in pixels) - Integration factor (for computing gravity and velocity) The rope's implementation topology is piecewise linear, which handy when it comes to adjust joints attributes (velocity, mass ...). No parametric representation is whatsoever needed, besides, the number of vertices can be dramatically improved without performance loss. Beware to decrease vertices interval in this case or the rope length will grow significantly.
b9bf97b9