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 39
    • Issues 39
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • iMSTK
  • iMSTKiMSTK
  • Issues
  • #194

Closed
Open
Opened Nov 08, 2018 by Nicholas Milef@NickMilefDeveloper

Add VisualModel to SceneObject

The current scene object implementation is causing too much data to be placed in the Geometry class. For instance, RenderMaterial and visibility functions should be moved out of the Geometry class. Currently, each SceneObject can only contain one visual geometry object. In order to overcome this, we proposed that each scene object can contain a vector of the new VisualModel class. Each VisualModel can contain a RenderMaterial and Geometry object.

Edited Nov 28, 2018 by Nicholas Milef
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#194