Segment Editor Paint tool stops working after the first stroke

Support
,
1

Hi everyone,

I am experiencing a strange issue with the Segment Editor in 3D Slicer.

When I create a new segmentation and use the Paint effect, the first paint stroke works correctly. However, immediately after that first stroke, the Paint tool stops working completely for that segmentation. I can still move the mouse and select the Paint tool, but no additional paint strokes are applied.

The same behavior happens if I create a completely new segmentation: the first paint stroke works, then the Paint effect stops applying any further changes.

So the problem does not seem to be limited to one specific segment or one specific segmentation. It looks like the Paint tool becomes unusable after the first edit.

I have already checked/tried the following:

  • The correct Source volume is selected.

  • The correct segment is selected.

  • Editable area is set to Everywhere.

  • Editable intensity range is disabled.

  • Modify other segments was tested with Allow overlap.

  • I tried creating a new segmentation from scratch.

  • I tried using different segments.

  • The issue still happens: only the first paint stroke works.

From the user interface, there is no obvious warning message. The tool simply stops modifying the segmentation after the first paint operation.

I am attaching a short screen recording showing the behavior.

My setup:

  • 3D Slicer version: 5.10.0

  • Operating system: [Windows]

  • Input data type: [DICOM]

  • Module: Segment Editor

  • Effect: Paint

Could this be related to a corrupted Segment Editor state, segmentation geometry, display scaling, masking settings, or a bug in this Slicer version?

Any suggestion on how to debug or fix this would be very helpful.

Thank you!

2

What happens you to go Data module, delete the existing segmentation object, right click on your volume and choose “Segment this” and then redo the segmentation?

3

Hi, thank you for your answer.

I tried many times and I tried this kind of way too, bu it seems to be stuck. I also tried to uninstall and do the installation again.

First it happened on a WorkStation and then when I tried to do a workaround by installing Slicer on a laptop after playing a bit it happened anyway and in the same way.

4

A lot of people are using the segment editor and this functionality daily on the v5.10.0 with the problem. So the chances are this problem is unique to your data and/or computer settings you are using. We might help more if you can share your data.

5

Unfortunately I can’t share my dataset. As far as the computer is concerned, I’m sure that the laptop has standard settings, maybe the bug is in the data, but this feels a little bit weird because I’m working on this data set for a bit and it started doing this at random time.

Any other kind of workaround?

Thank you for you time

6

Can you reproduce this issue on any public datasets? Does it happen on other data you have? Can you describe anything unizue about the data where this happens?

7

Hi could you link a public dataset where I can test this?

Meanwhile I think I can share a little video of what happens.

8

There are many datasets in the Sample Data module that you can choose from. The module is available in Slicer core, and there is a button from the Welcome module (“Download Sample Data” on the right side) when you start Slicer, easy to find.