Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • iMSTK iMSTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 69
    • Issues 69
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • iMSTK
  • iMSTKiMSTK
  • Issues
  • #110
Closed
Open
Created Jan 01, 2017 by Sreekanth Arikatla@sreekanth-arikatlaDeveloper

Optionally run controllers in a separate thread

At present the simulationManager runs controllers (including virtual coupling objects), collision detection, collision handling and solvers in a sequential fashion. For a scene where the solvers take more time the object controllers are called at a low frame rate leading to objects not responsive to the user movements. One option is to run the each controller in a separate module.

Whether the controllers are run in a separate thread within scene manager or a separate module they need to be synchronized for collision detection, handling and computation of forces.

Assignee
Assign to
Time tracking