# Transforming a volume makes it disappear from views

**URL:** <https://discourse.slicer.org/t/transforming-a-volume-makes-it-disappear-from-views/16133>\
**Category:** Support\
**Created:** [February 22, 2021, 12:52pm UTC](https://discourse.slicer.org/t/transforming-a-volume-makes-it-disappear-from-views/16133 "2021-02-22T12:52:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kanikayad15](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/kanikayad15/32/10026_2.png) [@kanikayad15](https://discourse.slicer.org/u/kanikayad15)\
**Post date:** [February 22, 2021, 12:52pm UTC](https://discourse.slicer.org/t/transforming-a-volume-makes-it-disappear-from-views/16133/1 "2021-02-22T12:52:12Z")

</div>

Currently trying to register two tiff files. Loaded them both in and set them at 50% opacity. Then I went into the transform module and tried rotating/moving one of the images, but when I move certain settings one of the images disappears off the screen (even when I revert the settings) . I scrolled out in the view screen and it looked like the two images were in completely different locations in the space. Why does this occur and how can I correct it? I’ve tried loading the images in with the centered option as well but I still run into this tissue.  
If it’s relevant, I’m running Version 4.11.20200930 r29402 / 002be18 on a Mac.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [February 22, 2021, 12:55pm UTC](https://discourse.slicer.org/t/transforming-a-volume-makes-it-disappear-from-views/16133/2 "2021-02-22T12:55:19Z")

</div>

> [@kanikayad15](#):
>
> I move certain settings one of the images disappears off the screen

What those certain settings were?

You can quickly and reliably [register images by placing a few landmarks](https://slicer.readthedocs.io/en/latest/user_guide/registration.html#semi-automatic-registration).

---

<div class="post-metadata">

**Author:** ![kanikayad15](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/kanikayad15/32/10026_2.png) [@kanikayad15](https://discourse.slicer.org/u/kanikayad15)\
**Post date:** [February 22, 2021, 4:12pm UTC](https://discourse.slicer.org/t/transforming-a-volume-makes-it-disappear-from-views/16133/3 "2021-02-22T16:12:07Z")

</div>

It varies per image pair but any of the translation or rotation sliders (LR, PA, IS) could result in this bug.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [February 22, 2021, 5:02pm UTC](https://discourse.slicer.org/t/transforming-a-volume-makes-it-disappear-from-views/16133/4 "2021-02-22T17:02:30Z")

</div>

Probably it is not a bug, but you move your images out from the slice view’s plane. If you work with 2D images then you can only translate along 2 axes and rotate around 1 axis without moving your image out of view.

If you want the view plane to follow the displayed image then you can use Volume reslice driver module (in SlicerIGT extension), but for registration you are much better off with using landmarks anyway.