::New();
// mImageData is vtkImageData with dimensions 143, 205, 165
mMapper->SetInputData(mImageData);
mActor->SetMapper(mMapper);
mActor->SetUserTransform(mTransform);
mActor->ForceOpaqueOn();
mRenderer->AddViewProp(mActor);
// This is how I change the slice being rendered.
mMapper->SetSliceNumber(index);
```
What I’ve noticed is that it doesn’t do it for the first slice:
Slice 0 (front view):
Slice 31 (at an angle, front view is completely gone):
---
### Author:  [@dgobbi](https://discourse.vtk.org/u/dgobbi)
#### Post date: [October 25, 2020, 4:27am UTC](https://discourse.vtk.org/t/vtkimagedata-rendering-disappears-when-viewed-from-z-axis/4480/4 "2020-10-25T04:27:55Z")
Yes, I’m sure now that it’s a near/far clipping plane issue.
If you do not set up the camera yourself, then VTK will automatically set up the camera based on the actor bounds during the first render. For vtkImageActor, the bounds are set from the DisplayExtent of the actor. Since the DisplayExtent is a single slice, this causes the near and far clipping planes to be very tightly positioned in front of and behind the slice.
There are certain interactions that cause the interactor to reset the clipping planes (I can’t recall which), but it’s very easy for at least part of the vtkImageActor to move beyond the clipping planes. There are two work-arounds for this:
1. Set up the camera yourself before the first render, and set the clipping range to be large enough to contain the whole image from any angle.
2. Use vtkOutlineFilter to create a frame around the image data (use the image data as the input to vtkOutlineFilter, and for the outline actor, use the same UserTransform as for the image actor). This extra actor will cause VTK to initialize the near/far clipping to better values. You can make it transparent if you don’t actually want it to be visible.
---
### Author:  [@Velchivz](https://discourse.vtk.org/u/Velchivz)
#### Post date: [October 25, 2020, 6:32pm UTC](https://discourse.vtk.org/t/vtkimagedata-rendering-disappears-when-viewed-from-z-axis/4480/5 "2020-10-25T18:32:30Z")
Thanks for the suggestion. I tried doing the second one, but once I make the frame invisible, the clipping problem returns 😔
In terms of the first suggestion, would I have to compute the clipping plane based on the position of the camera with respect to the visuals? I sometimes also render other objects along the image (and in some scenarios, multiple images). Would one require to also compute the clipping range when the user zooms in and out?
---
### Author:  [@dgobbi](https://discourse.vtk.org/u/dgobbi)
#### Post date: [October 25, 2020, 7:52pm UTC](https://discourse.vtk.org/t/vtkimagedata-rendering-disappears-when-viewed-from-z-axis/4480/6 "2020-10-25T19:52:30Z")
> [@Velchivz](#):
>
> Thanks for the suggestion. I tried doing the second one, but once I make the frame invisible, the clipping problem returns
Try an opacity of 0.005. Regarding the camera, you can look through the VTK examples e.g. [https://lorensen.github.io/VTKExamples/site/Cxx/VisualizationAlgorithms/CarotidFlow/](https://lorensen.github.io/VTKExamples/site/Cxx/VisualizationAlgorithms/CarotidFlow/)
---
### Author:  [@Velchivz](https://discourse.vtk.org/u/Velchivz)
#### Post date: [October 27, 2020, 12:00am UTC](https://discourse.vtk.org/t/vtkimagedata-rendering-disappears-when-viewed-from-z-axis/4480/7 "2020-10-27T00:00:54Z")
Okay, thank you. I will try these and see what works best. At least I know what the issue is.