-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Bugs with VTK 9 #7599
Comments
FWIW, PyVista worked "out of the box" this way, while Mayavi fails to compile (which I'll look into) :) |
Can someone else on macOS see if you can replicate https://gitlab.kitware.com/vtk/vtk/-/issues/17846 ? |
Thanks for starting this @larsoner. I'll follow the procedure you explained to be better prepared for VTK 9. Also relevant for pyvista/pyvista#562 |
Can you share that data or how to launch that scene? I'll try to look into this and see what's happening to the overlain mesh. |
WARNING: Will download 1.5 GB of data to
You will probably need to This is the code I was using (last I recall!), but for some reason now it hangs when I try it. |
(FYI I forgot a |
Sorry I am late, I had to build everything from scratch and follow your instructions. This is the result of:
EDIT I created |
after these three steps you should be in |
Exactly. |
I disabled depth peeling explictly without success: ren_win = self.plotter.ren_win
ren_win.SetAlphaBitPlanes(0)
renderer = self.plotter.renderer
print(renderer.GetLastRenderingUsedDepthPeeling()) # prints 0
renderer.SetUseDepthPeeling(0) |
Using offset like we did with Vispy does work for me, I'll open a PR: mapper.SetResolveCoincidentTopologyToPolygonOffset()
mapper.SetRelativeCoincidentTopologyPolygonOffsetParameters(-4., -4.) |
vtk-build starts out empty, but the cmake line populates it. I wonder if your problems were due somehow to building in a subdirectory of the source directory, rather than a totally separate one |
What's interesting about the topology problem is that I don't see it on mayavi. But whatever makes it work I guess! |
Any idea how they deal with it? |
No idea |
VTK9 rc3 wheels are up so you can try @GuillaumeFavelier : For me the It occurred to me that we actually need to fix this soon because once VTK9 wheels land on PyPi and are incorporated by Anaconda, anyone who installs or upgrades MNE will be stuck with unusable plotting :( Can you look into it? |
I'm on it |
@larsoner I installed it and I have an issue with picking:
But except from that, the app is completely interactive. All the sliders and tool bar buttons work and are linked correctly. |
Hmm, must be some issue with my system. What's your |
|
And I use |
Ahh right without |
Hooray! With |
Feel free to try #7665 then. It worked for me. |
@GuillaumeFavelier looks like the topology problems are still there: |
@GuillaumeFavelier might be good to fix this before looking into |
For future reference, the visual issues mentioned in #7599 (comment): |
@GuillaumeFavelier you can now pretty easily build and install VTK 9 (which is good because they are on RC3, and it should fix some bugs and bring 3.8 support):
However, there is at least one rendering bug (depth peeling again maybe?) where the surface overlay gets cut off at some distance based on rotation (note the rightward "v" cut of the overlay):
We might need to figure out how to properly resolve the coincident topology here -- relying on VTK to do it automagically might not work anymore. Or maybe it's something else...?
The text was updated successfully, but these errors were encountered: