In the Rigid Registration View, when the Versor3DRigidTransform together with the Versor3DRigid optimizer is selected, both moving and fixed image 3D & short --> the application runs into an 'wrong pixel type' exception thrown by ImageSource ( ImageToItk macro most probably ).
Same behavior also for Affine, but it works for Euler3D + RegularStepGradientDescent