Afraid not. One potential work around would be you build the
transformation matrix and set that on the camera. You can build the
matrix yourself by changing the order of rotations.
Utkarsh
On Fri, Nov 24, 2017 at 1:43 PM, Léo Pessanha
wrote:
> Thank you again for
Thank you again for your help, Utkarsh!
Your solution worked but it flicks a lot because of the gimbal lock, but I
believe I could not get rid of that. Right?
Thanks in advance!
Leonardo Pessanha
Laboratory of Computational Methods in Engineering
Federal University of Rio de Janeiro - COPPE
Rio
Leo,
To handle 90-degree pitch or elevation, do the following:
camera.Pitch(90)
camera.OrthogonalizeViewUp()
Render()
Utkarsh
On Tue, Oct 24, 2017 at 2:50 PM, Léo Pessanha
wrote:
> Thanks Utkarsh!
>
> This change would take a build right? Can't do it right now
Thanks Utkarsh!
This change would take a build right? Can't do it right now =/
My goal is to know what should I do after a
cameraInstance.Pitch(90)
>
and before a
Render()
>
In order not to get the warning
Resetting view-up since view plane normal is parallel
>
I've tried
Leo,
You can't access it in Python since the Python script is not run on the
server side. If your goal is to debug what thet camera is set to, you can
put cout's to print the camera in
`vtkCaveSynchronizedRenderers::HandleStartRender`. That's where the local
camera on each rank is "prepped" for
Hi!
I would like to know if there's a way to acess the information/attributes
of the cameras there are created trough a .pvx file
To acess the attributes in the camera of the active Layout/RenderView I do:
1 - Open Python Shell
2 - camera = GetActiveCamera()
3 - print(camera)
And the output