I recently upgraded from 5.13.3 to 6.0 and the slice filters I was using to create animations are no longer working.
The way I use the tool is I use the slice to create a X/Y/Z plane in my domain, then I create an animation using the Time Manager of this slice using a Slice Type Offset, which then gives me an animation of that slice throughout my specified X/Y/Z range.
Now on 6.0 the slice only works on my initial specified plane location, but if I change the time manager to a different frame it just comes out blank.
I would prefer to have this working on 6.0 as I enjoy the other improvements, especially the dark mode and improvements to the Ensight reader. Did the implementation of the animations change or should I be doing something differently?
My “number of frames” variable is set to 150. So now results only show up at frame 0, but no other frames. I tried setting it to 1, 10, 150 with no change. I run a sweep 6m long, so I use 150 frames to get increments of 40mm.
Also, by any chance would you know the Python command to change the number of frames variable? I have done a lot of traces to track that down but have never been able to find it.
I uploaded a simplified state I use and a couple screenshots. If I run this same state using 5.13.3, it shows data through every frame. On 6.0 it only shows the data for frame 0.
To recreate the problem:
Load data to the target case (I didn’t include mine since it’s around 50GB and proprietary, but you can use any simple data set)
In the RenameArrays2 filter call a variable cp2.
Then show X Animation - Cp
You may have to change the origin of the first slice if your data set is a lot smaller than mine (default is -1.5m from the origin)
In the time manager show frame 0 and see if the data show correctly
Then sweep through a couple different frames and it should be empty
This is caused by invalid cells in your dataset that the clip filter is unabled to handle, my guess would be on non-manifold polyhedron but more investigation needed to understand that.
There was some change to the handling of polyhedrons in VTK, these change made the storing of polyhderon more efficient but required some reimplementation of methods, that may have worked by chance on invalid polyhedron before the change.