I had Slicer 4.10.2 version on my PC. After a while, I noticed that for some images the uploading time is too slow, so I installed the latest stable version 4.11.2. In the latest version, I have no problem with the uploading time, but I noticed a difference in how these two versions display the volume in the volume rendering module (screenshot attached, on the left - 4.10.2, on the right - 4.11.2). Slicer 4.10.2 seems to provide more accurate volume rendering (less noise, smoother texture). I noticed that for these two versions, the scalar opacity and scalar color mapping are different for the same image, so the reason seems to be in the fact how the default values are set for the opacity and color.
Could you please tell me why the renderings are different and what I should do to get the same visualization in the latest stable release as in 4.10.2? I know I can adjust the visualization manually, but it would be nice to get a nice visualization like in 4.10.2 without any effort.
Note. This screenshot is only to show the difference - unfortunately, for confidential reasons I cannot post images where this difference is more noticeable.
Both these renderings seem to just use the default grayscale mapping, based on the current window/level value. The default window/level detection method was slightly improved in Slicer-4.11, which may explain the difference in the default volume rendering preset. You can edit this setting in Volume rendering module: move the Shift slider and optionally also adjust Scalar Opacity Mapping function in Advanced/Volume properties section (see documentation).
However, I would strongly recommend to choose a volume rendering preset (Volume rendering module / Display / Preset) and use Shift slider to adjust it to your image.
Thank you for the reply. I was trying to choose a preset but none of them work - the image disappears or turns into the black cube, my guess is that this is due to the fact that all of my images are normalized to the 0…1 range. Shift without any preset doesn’t work also (i think this is for the same reason).
Are there any ways to fix it? Maybe I can somehow adjust the scale or return the W/L detection method to the old one?
