Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,758
    • Issues 1,758
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 68
    • Merge Requests 68
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #14206

Closed
Open
Opened Aug 03, 2013 by Kitware Robot@kwrobotOwner

GPU based Volume Rendering always use the first data array for coloring

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


The problem arise when volume rendering a cartesian-grid dataset with multiple scalar arrays. If the GPU based volume rendering is selected, it does not matter what scalar array is selected for coloring, Paraview always use the same one. For example, if there are Temperature, Pressure and Velocity magnitude, Paraview will always show the Temperature attribute, even when pressure or Velocity magnitudes are selected. All the other kinds of volume renderer (Ray cast and Texture mapping) work correctly.

This happens both on my laptop (NVIDIA GT540M / driver 306.94) and my desktop (NVIDIA GTX580 / driver 314.7)

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: paraview/paraview#14206