Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,961
    • Issues 1,961
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #20193
Closed
Open
Issue created Sep 08, 2020 by Boonthanome Nouanesengsy@boonthDeveloper

Paraview able to goto next timestep when only one timestep is loaded

When only one timestep is loaded, in Paraview, you can still hit the VCR control for next timestep. The time will change from 0 to 0.1111, 0.2222, etc., until you hit 1.

To reproduce, you can create a wavelet dataset, then try to click on the next timestep button on the VCR controls. The data does not seem to change for wavelet, but if I load a random vtm file, it looks like junk data is being loaded for the "other timesteps".

This occurs on the latest master of Paraview.

@patchett2002 @cory.quammen

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking