I also get the problem with other meshes, I’ve tried logging the point size that I just set and I get a correct programmatic output, but no correct behavior…
If that works, my hunch is right. I’ve always thought there was a bug where the opengl polydata mapper only respected the vertex visibility setting when edge visibility is switched on. Let me know what you see. I think this is an easy fix.
VTK 9.4 was just released a few days ago but it’s release candidates have been out for some weeks now, so I thought you were testing those wheels. One of the features in that that is you can access member variables without using the Set/Get functions.
Hi, i need more information to understand what’s causing this behavior. What does vtkRenderWindow().GetClassName() output? Whats the operating system? Do you have a physical display or is it in a headless configuration? What GPU are you using? Did you build the VTK python yourself? If so what cmake settings did you use? or is it from pypi?
vtk.vtkRenderWindow().GetClassName() vtkXOpenGLRenderWindow
OS => Ubuntu 22.04.5 LTS
It is physical display
GPU => NV167 / Mesa Intel® Xe Graphics (TGL GT2)
I installed it from Pypi
If i understand correctly, you’re able to render polygons and lines fine, but not points? It could be a driver issue. Can you share output of glxinfo -B? You can get that from sudo apt install mesa-utils