Issue with Contour Display in 3D Slicer

Hi everyone,

I recently encountered an issue when trying to open CT images and their corresponding RT structures, exported from MIM software version 7.0.10, in 3D Slicer version 5.6.1 with extension of Slicer RT (version: dbbdffd 2023-12-12).

The problem I’m facing is that when I load these files into 3D Slicer, zigzag lines appear for the ring contour around the body and skin. Additionally, the contour becomes opaque at certain slices. The image above is the body contour ring become opaque at certain slices. I’m puzzled by this behavior and wondering if anyone has encountered a similar issue or knows what might be causing it.

Any insights or suggestions on how to resolve this would be greatly appreciated. Thank you!

Can you please check the planar contour representation?

The Representations section in the Segmentations module should look like this (make sure you select the correct segmentation on the top):
image

Center the 3D view to make the segmentation show up (or find the reason why it does not show in 3D)/

Show the planar contour representation:
image

You should see something like this:
image

If something is not right, please send us screenshots.

Thanks for your reply.

I made adjustments to ensure the 3D view displays correctly. The image above depicts the skin segmentation. However, zigzag lines are present, which deviate from the intended segmentation—a perfect ring surrounding the skin on the CT image. Additionally, while there should be a perfect ring visible, the entire section appears shaded instead.

The axial plane shown in the figure above is the actual segmentation. I’ve noticed that the segmentation becomes shaded at certain slices when I navigate through slices (same problems existed on 3 planes) in 3D slicer.

I’m puzzled as to why this zigzag line and distortion are occurring. Any further insights or suggestions would be greatly appreciated.

I was trying to help figure out the root cause of the issue. If the lines appear correctly, then the original representation in the file is right, and the problem is in the conversion. It would be useful to know this.