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 71
    • Issues 71
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • 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
  • #73
Closed
Open
Created Sep 26, 2016 by Nicholas Milef@NickMilefDeveloper

Texture manager

  • In iMSTK textures are loaded on a per-mesh basis. This means that meshes that share textures have redundant texture loading.
  • This can reduce drawcalls down the line, but that's not a priority right now.
  • The implementation will be a hashtable of the file name because it's faster than doing texture compares. This will all be done behind the scenes.
Assignee
Assign to
Time tracking