Skip to content
GitLab
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 83
    • Issues 83
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • iMSTKiMSTK
  • iMSTKiMSTK
  • Issues
  • #370
Closed
Open
Issue created Sep 21, 2021 by Andrew Wilson@andrew.wilson🐘Contributor

CDDebugObject Queue instead of Clear Rates

The CDDebugObject is an object that quickly adds/removes geometry to represent collision data (contacting faces, edges, etc). This is for debug purposes.

Unfortunately when you have a simulation running at 1000 updates a second its hard to see whats going on. One might slow it down, advance by key, or one of the solutions currently provided is a "clear rate". Which clears the collision data visual representations every N frames. So you can see the last say, 50 frames.

A more intuitive implementation would be a queue. Such that you can store the last 50 collision data representations. Unfortunately this is a bit tricky to implement efficiently.

Edited Jun 01, 2022 by Andrew Wilson
Assignee
Assign to
Time tracking