Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Mask only partially visible when loaded #717

Closed
xibeishun opened this issue Mar 14, 2025 · 3 comments · Fixed by #719
Closed

Mask only partially visible when loaded #717

xibeishun opened this issue Mar 14, 2025 · 3 comments · Fixed by #719

Comments

@xibeishun
Copy link

Image

Description:
When loading a segmentation mask in VolView, some masks are only partially displayed. The issue is observed as follows:
Some regions of the mask are not correctly rendered.
The same data displays correctly in other visualization tools (e.g., ITK-Snap, 3D Slicer).
The issue persists across different mask file formats (NIFTI).

Steps to Reproduce:
Load a 3D segmentation mask file (e.g., NIFTI format) in VolView.
Observe the mask rendering result.
Notice that part of the mask is missing or not displayed correctly.

@PaulHax
Copy link
Collaborator

PaulHax commented Mar 14, 2025

Yikes. Looks like a bug during rendering. Do you happend to have some files to share with this problem? Background and the segmentation 🙏

@xibeishun
Copy link
Author

Thanks for your response! Yes, this issue seems to be rendering-related. I have prepared some example files that demonstrate the problem, including both the background image and the segmentation mask.

data
mask

PaulHax added a commit to PaulHax/VolView that referenced this issue Mar 17, 2025
Also, put segmentation slices on top.

Closes Kitware#717
@PaulHax
Copy link
Collaborator

PaulHax commented Mar 19, 2025

@xibeishun Thanks for the files. This issue is fixed on main branch and at https://volview-dev.kitware.app/

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants