Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
iMSTK
iMSTK
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • iMSTK
  • iMSTKiMSTK
  • Issues
  • #141

Closed
Open
Opened 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

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: iMSTK/iMSTK#141