Skip to content
GitLab
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 83
    • Issues 83
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • iMSTKiMSTK
  • iMSTKiMSTK
  • Issues
  • #319
Closed
Open
Issue created May 25, 2021 by Andrew Wilson@andrew.wilson🐘Contributor

Remove Vulkan

As it stands Vulkan in iMSTK doesn't work. It really doesn't seem like we'll be able to realistically support this. We'd sooner support Unity or Unreal which can be used for more graphical performance/fidelity. If this is the case, some other 3rd party module of iMSTK should be used if anyone wants to develop this.

Not to mention VTK has been making progress in rendering fidelity. I'm confident we'll be able to write some custom shaders for it in the future. But there are a few hard limits to what VTK can do currently. These things can be done in Unity and Unreal though. Also worth mentioning there are few things that VTK can do that Unity/Unreal can't (without 3rd party or other bad solutions), namely Volume Rendering which would be particularly difficult to support on Vulkan.

Edited May 25, 2021 by Andrew Wilson
Assignee
Assign to
Time tracking