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 67
    • Issues 67
    • 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
  • #141

Closed
Open
Created May 04, 2017 by Nicholas Milef@NickMilefDeveloper

Moving normal/tangents calculations out of the render thread

I discussed this a little with Alexis on Tuesday, but I've been encountering performance issues with normal recalculation. Right now, when a deformable mesh gets rendered, it must meet recalculate the normals (and soon, the tangents as well) as part of the render loop. IMO, this shouldn't happen in the render loop since the render loop should only be issuing draw commands and doing culling related things.

I was thinking that it might not be bad to move that command to the physics module since recalculation could be done under a certain threshold. Or, we could move it to another module that solely does mesh preparation. What do you all think?

@sreekanth-arikatla @MohitTyagi @alexis-girault

Assignee
Assign to
Time tracking