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,666
    • Issues 1,666
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 62
    • Merge Requests 62
  • 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
  • #15642

Closed
Open
Created Aug 12, 2015 by Kitware Robot@kwrobotOwner

Multiblock Exodus data not always colored by vtkBlockColors

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


With the upcoming release of ParaView 4.4, when you load an Exodus file the default coloring is vtkBlockColors instead of a solid color. This usually works, but sometimes does not. Here is a case where the default color sometimes reverts back to solid color.

  1. Load can.ex2. Apply.
  2. Split the view (either vertically or horizontally, it doesn't matter).
  3. In the new view, make can.ex2 visible.

In the new view, the can data have a solid color instead of being colored by vtkBlockColors.

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