Fix rendering of overlay on some graphic chipsets. #286
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ok. More digging and potential solutions.
An undocumented workaround for various rendering bugs in some graphics drivers is to hack your local
site-packages/vtkmodules/qt/__init__.py
file and make this change:Code relying on
vtkmodules
, such as Mayavi and pyvista, will check theQVTKRWIBase
variable and try to do the right thing accordingly. Unfortunately, for some reason, it decided to do this:I don't know where the
QOpenGLWidget
/QGLWidget
confusion comes from, but in my case, it needs to beQGLWidget
, otherwise everything crashes. Removing this try/catch construction and just importingQGLWidget
fixes this at my end.This gets me up to this point:
Depth ordering bugs are fixed! And now I face the a similar rendering bug as @filip-halemba reported in #284. Sadly, turning on backface culling on the overlay surface had no effect for me. However, turning on
force_opaque
did work! See changes in this PR.Perfection at last!
EDIT:
Closes #284