Rendering changes between 9.2.6 and 9.3.0?

I have a Python / PySide6 / VTK application that renders unstructured grids and I’ve noticed a change of behavior when using 9.2.6 and 9.3.0 and I’m trying to track down what changed and how to fix it.

In 9.2.6, I can load in large grids (>30M cells) and it rotates seamlessly. In 9.3.0, with the exact same code, and just the VTK version changed, the model can’t rotate at all. In smaller models, there’s a terrible lag when trying to rotate it.

I got the wheels from pypi and installed using pip. It makes me think that it’s not using hardware rendering for me with 9.3.0, and is for 9.2.6, but I’m not sure how to prove it.

I read through the release notes for 9.3.0, and I saw the mentions about OSMesa but don’t see anything else obvious on why I’d see this change in performance.

Any ideas?

After the vtkRenderWindow has rendered, call window.ReportCapabilities() and print the result. If the information matches your GPU and driver, then hardware rendering is in use.

Thank you. It returns the exact same thing for me in both versions. The whole process did help me track down what the issue is. So this question is closed.

It has to do with an actor I have that does point labeling. The actor was mistakenly left as visible at the beginning, even though it wasn’t labeling anything yet. This wasn’t an issue in 9.2.6, but for some reason was 9.3.0. I’m guessing something isn’t quite right with my pipeline, but turning that actor off got me back to the performance I was expecting.

Thanks for the quick answer!

Did this involve vtkLabeledDataMapper ?

No. I used vtkLabelPlacementMapper combined with vtkPointSetToLabelHierarchy to place my labels.

1 Like