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 63
    • Issues 63
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • 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
  • #80

Closed
Open
Created Sep 26, 2016 by Nicholas Milef@NickMilefDeveloper

Mesh movement /scaling

  • Currently, for all geometry objects, the translate/rotate/scale function only set corresponding variables, which is then taken by the VTK renderer for visual rendering.
  • “Real transform” is needed for scenario like collision detection and handling. Currently in imstk-ETI, it is done vertex-by-vertex for the laryngoscope mesh.
  • Need a function to apply the translate/rotate/scale at geometry/mesh level. Need to figure out how to avoid the renderer re-applying those transformation again.
  • Also, GPU only transformations for static meshes
Assignee
Assign to
Time tracking