Here is another video illustrating that the renderer and the camera works fine with models. So the problem is probably in the slice widget in the 3D view.
https://dl.dropbox.com/u/7771079/SlicerClippingBug2.mp4

Some info that may help in finding the root cause of the issue: If you first apply the transform and then turn on the slice visibility then the problem does not occur (but if you change the transform later then the problem occurs again). So, it seems that some position-dependent initialization is performed when the slice is first shown and that is not performed again when the applied transform changes.

My brief investigation didn't produce any leads. Here is some additional information:

• it is easier reproduce in 4-up layout. If I start in conventional layout I was able reproduce it once out 4-5 tries.
• if I save the scene in "slice not visible" state and load it back the problem does not occur (even after restarting slicer)
• there seems to be no difference in MRML process events if the slice is rendered or not.
• resetting clipping plane in camera does not help.
• I can reproduce it with or without additional models. The models are always visible unlike slices.

Email sent to: Alex Yarmarkovich, Tamas Ungi, Julien Finet, Steve Pieper

Hi Folks,

Following yesterday hangout, the plan is to organize a "mini-bugfest" on Friday morning to work together on issue 2785.

See http://www.na-mic.org/Bug/view.php?id=2785

The plan would to use Google Hangout from 10am to noon. Let me know if you have can't attend.

Thanks
Jc

In vtkMRMLSliceLogic::ProcessLogicEvents() call Modified on vtkPoints to force slice bounds update.
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21473

Back ported to 4.2 branch. See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21474

Closing resolved issues that have not been updated in more than 3 months