-
Notifications
You must be signed in to change notification settings - Fork 110
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
Opacity is broken in Scalable Rendering Mode #19498
Comments
Yeah, I have a bad feeling we introduced some transparency issues in 3.4 with VTK-9. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
I am seeing this issue with isosurfaces that have less than 100% opacity in 3.4.1. Is this fully fixed by #19583? I have to ask the TACC sysadmins to re-build the VisIt module, so I want to confirm that this is really fixed. If there are nightly builds I can test, let me know. |
Yes, #19583 addressed the issue with the missing polygons and the horizontal bars, but there is still an issue with low opacity showing up white. I am looking into that. |
In 3.4.1 blueOS and toss4, scalable rendering mode with non-100% opacity is broken.
Here is a pseudocolor plot of
d
frommulti_curv3d.silo
with the opacity set to 20% in default rendering mode:Here is the same plot with scalable rendering mode enabled:
Here is a filled boundary plot of
mat1
frommulti_curv3d.silo
with the opacity set to 20% in default rendering mode:Here is the same plot with scalable rendering mode enabled:
Another angle:
These plots worked correctly in 3.3.3.
To reproduce:
multi_curv3d.silo
d
There are some large datasets on the SCF under
/usr/workspace/visit/visit/bug_data
that have these issues; we should ensure that for all of them this issue is resolved before marking this ticket as resolved. It is possible that those datasets may have additional issues that are not captured here.The text was updated successfully, but these errors were encountered: