Usually, and in Slicer stable, when loading a volume of any dimension, the slice views would fit the extent of the volume nicely.
That’s no longer the case since recently. The image below shows the effect when a small volume is loaded (212 x 92 x 114) with spacing 0.6 x 0.6 x 0.6: on loading, with FitSliceToAll() and with FitSliceToBackground().
It seems that the problem is with FitSliceToAll(). Formerly, it would behave like FitSliceToBackground(). Is it how it should be considered now, a feature?
Slicer is started with --ignore-slicerrc and the slice composite node has a single background scalar volume node. Using self-built preview on Linux.
Sure, here is one, cropped from CTA-cardio. I just tested with 5.7.0-2024-11-15 r33115 / 7438bf2 from your website with the same unexpected result. It’s not a big issue, I just reported it in case there might be something to fix.
I can confirm this is a regression - the nightly preview is first below, and the latest 5.6.2 release is below that. All I did was drag-and-drop the file provided by @chir.set on each.
Indeed, Reset to field of view does not work for this volume. How to reproduce: link slice views, click Reset to field of view button in any of the slice views.
@chir.set to make sure we take care of this before the new stable release, would you mind submitting a bug report to issues.slicer.org and post the link here? Thank you!
