Skip to content
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

Closed
JustinPrivitera opened this issue May 7, 2024 · 11 comments · Fixed by #19596
Closed

Opacity is broken in Scalable Rendering Mode #19498

JustinPrivitera opened this issue May 7, 2024 · 11 comments · Fixed by #19596
Assignees
Labels
bug Something isn't working impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) likelihood medium Neither low nor high likelihood reviewed Issue has been reviewed and labeled by a developer
Milestone

Comments

@JustinPrivitera
Copy link
Member

JustinPrivitera commented May 7, 2024

In 3.4.1 blueOS and toss4, scalable rendering mode with non-100% opacity is broken.

Here is a pseudocolor plot of d from multi_curv3d.silo with the opacity set to 20% in default rendering mode:
image

Here is the same plot with scalable rendering mode enabled:
image

Here is a filled boundary plot of mat1 from multi_curv3d.silo with the opacity set to 20% in default rendering mode:
image

Here is the same plot with scalable rendering mode enabled:
image

Another angle:
image

These plots worked correctly in 3.3.3.

To reproduce:

  1. run visit in parallel
  2. open multi_curv3d.silo
  3. make a pseudocolor plot of d
  4. change opacity to 20%
  5. open options/rendering and turn scalable rendering mode to "always"

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.

@JustinPrivitera JustinPrivitera added bug Something isn't working likelihood medium Neither low nor high likelihood impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) labels May 7, 2024
@markcmiller86
Copy link
Member

Yeah, I have a bad feeling we introduced some transparency issues in 3.4 with VTK-9.

@JustinPrivitera

This comment was marked as outdated.

@JustinPrivitera

This comment was marked as outdated.

@JustinPrivitera

This comment was marked as outdated.

@JustinPrivitera

This comment was marked as outdated.

@JustinPrivitera

This comment was marked as outdated.

@JustinPrivitera JustinPrivitera added this to the 3.4.2 milestone May 15, 2024
@JustinPrivitera

This comment was marked as outdated.

@JustinPrivitera

This comment was marked as outdated.

@JustinPrivitera JustinPrivitera changed the title Opacity Slider produces wrong results Opacity is broken in Scalable Rendering Mode May 22, 2024
@cyrush cyrush added the reviewed Issue has been reviewed and labeled by a developer label Jun 4, 2024
@BenWibking
Copy link
Contributor

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.

@JustinPrivitera
Copy link
Member Author

JustinPrivitera commented Jun 10, 2024

#19583 addressed this ticket but it sounds like there is another opacity issue affecting the first of the three user data sets (merged mili data set where low opacity makes it white). Should we open a new ticket for that? @brugger1 @visit-dav/visit-developers

@brugger1
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) likelihood medium Neither low nor high likelihood reviewed Issue has been reviewed and labeled by a developer
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants