MantisBT - ParaView
View Issue Details
0005576ParaView(No Category)public2007-08-27 06:092011-01-13 17:00
Jean M. Favre 
Utkarsh Ayachit 
normalminoralways
closedfixed 
 
3.43.4 
0005576: 3D trackball motion is jerky when bounding box exceeds [1e13,1e13,1e13] range
When loading data whose bounding box exceeds the [1e13,1e13,1e13] range, the trackball motion on the 3D view is jerky, making it impossible to do precise positioning. Anydata smaller in bounding volume is fine.

tested with ParaView3 cvs version of August 27, 2007
The attached pvsm state, when loaded in PV3 demonstrates the problem.

The scale factor of the Transform filter can be edited (all 3 values changed from 1e13 to 1e12) and the jerkiness disappears.

Thanks for looking a this.

JeanF
No tags attached.
related to 0006233closed Utkarsh Ayachit Data that has a VERY small scale doesn't display and resize properly. 
? jerky.rotation.pv3.1.1.pvsm (98,142) 2007-08-27 06:09
https://www.vtk.org/Bug/file/6124/jerky.rotation.pv3.1.1.pvsm
? jerky.rotation.pv3.2.1.pvsm (99,468) 2007-11-21 05:45
https://www.vtk.org/Bug/file/6233/jerky.rotation.pv3.2.1.pvsm
? jerky.rotation.pv3.3.0.pvsm (61,590) 2008-06-20 11:53
https://www.vtk.org/Bug/file/6545/jerky.rotation.pv3.3.0.pvsm
Issue History
2007-08-27 06:09Jean M. FavreNew Issue
2007-08-27 06:09Jean M. FavreFile Added: jerky.rotation.pv3.1.1.pvsm
2007-08-29 16:07Berk GeveciAssigned To => Berk Geveci
2007-08-29 16:07Berk GeveciStatusbacklog => tabled
2007-11-21 05:45Jean M. FavreFile Added: jerky.rotation.pv3.2.1.pvsm
2007-11-21 05:48Jean M. FavreNote Added: 0009716
2008-03-10 12:57Berk GeveciAssigned ToBerk Geveci => Utkarsh Ayachit
2008-04-14 17:17Berk GeveciAssigned ToUtkarsh Ayachit => Berk Geveci
2008-04-14 17:17Berk GeveciCategory => 3.4
2008-04-14 17:22Clinton StimpsonRelationship addedrelated to 0006386
2008-04-14 17:22Clinton StimpsonRelationship deletedrelated to 0006386
2008-05-29 13:18Berk GeveciRelationship addedrelated to 0006233
2008-06-03 11:08Utkarsh AyachitAssigned ToBerk Geveci => Utkarsh Ayachit
2008-06-20 11:10Utkarsh AyachitStatustabled => @80@
2008-06-20 11:10Utkarsh AyachitResolutionopen => fixed
2008-06-20 11:10Utkarsh AyachitNote Added: 0012443
2008-06-20 11:51Jean M. FavreStatus@80@ => @20@
2008-06-20 11:51Jean M. FavreResolutionfixed => reopened
2008-06-20 11:51Jean M. FavreNote Added: 0012447
2008-06-20 11:53Jean M. FavreFile Added: jerky.rotation.pv3.3.0.pvsm
2008-06-20 11:56Jean M. FavreNote Edited: 0012447
2008-06-20 13:59Utkarsh AyachitStatus@20@ => @80@
2008-06-20 13:59Utkarsh AyachitResolutionreopened => fixed
2008-06-20 13:59Utkarsh AyachitNote Added: 0012448
2008-06-23 21:37Alan ScottStatus@80@ => closed
2008-06-23 21:37Alan ScottNote Added: 0012491
2009-05-13 13:58Utkarsh AyachitTarget Version => 3.4
2009-05-13 13:59Utkarsh AyachitFixed in Version => 3.4
2011-01-13 17:00Source_changeset_attached => VTK master a2bd8391
2011-01-13 17:00Source_changeset_attached => VTK master 020ef709
2011-06-16 13:10Zack GalbreathCategory => (No Category)

Notes
(0009716)
Jean M. Favre   
2007-11-21 05:48   
I updated the script file to work with the release 3.2.1.
It is a real pain to work with AMR data and very large grids with this jerky trackball motion. Could this be looked at for 3.2.2?

I did not mention it in my original post, but this jerkyness does not appear in a standard C++ VTK test. It shows up only in ParaView.
(0012443)
Utkarsh Ayachit   
2008-06-20 11:10   
Do the trasformation in normalized space to avoid precision issues.

/cvsroot/ParaView3/ParaView3/VTK/Rendering/vtkCamera.cxx,v <-- VTK/Rendering/vtkCamera.cxx
new revision: 1.114; previous revision: 1.113


/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVGenericRenderWindowInteractor.cxx,v <-- Servers/Filters/vtkPVGenericRenderWindowInteractor.cxx
new revision: 1.7; previous revision: 1.6
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVGenericRenderWindowInteractor.h,v <-- Servers/Filters/vtkPVGenericRenderWindowInteractor.h
new revision: 1.7; previous revision: 1.6
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVInteractorStyle.h,v <-- Servers/Filters/vtkPVInteractorStyle.h
new revision: 1.5; previous revision: 1.4
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVJoystickFly.cxx,v <-- Servers/Filters/vtkPVJoystickFly.cxx
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVJoystickFly.h,v <-- Servers/Filters/vtkPVJoystickFly.h
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVTrackballPan.cxx,v <-- Servers/Filters/vtkPVTrackballPan.cxx
new revision: 1.3; previous revision: 1.2
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVTrackballRoll.cxx,v <-- Servers/Filters/vtkPVTrackballRoll.cxx
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVTrackballRotate.cxx,v <-- Servers/Filters/vtkPVTrackballRotate.cxx
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVTrackballRotate.h,v <-- Servers/Filters/vtkPVTrackballRotate.h
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVTrackballZoom.cxx,v <-- Servers/Filters/vtkPVTrackballZoom.cxx
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVTrackballZoom.h,v <-- Servers/Filters/vtkPVTrackballZoom.h
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkTrackballPan.cxx,v <-- Servers/Filters/vtkTrackballPan.cxx
new revision: 1.2; previous revision: 1.1
(0012447)
Jean M. Favre   
2008-06-20 11:51   
(edited on: 2008-06-20 11:56)
I updated cvs

tried the simple script I had provided and the problem is gone.

tried our AMR data, and the whole display disappears AFTER the first redraw. Reset Camera has no effect.

I upload a test pvsm state. It creates a hierarchical dataset, and transforms it to astro-physics size, i.e. multiply by 1e13. The whole display disappears.

(0012448)
Utkarsh Ayachit   
2008-06-20 13:59   
Another attempt to fix this issue. On loading the attached state, PV is still in a funny state, however doing a ResetCamera fixes the issue. I am guessing the camera position/focalpoint/clip planes values saved in state are computed incorrectly due to the bug in earlier implementation.

/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPVTrackballRotate.cxx,v <-- Servers/Filters/vtkPVTrackballRotate.cxx
new revision: 1.3; previous revision: 1.2
(0012491)
Alan Scott   
2008-06-23 21:37   
As per Utkarsh's note listed at the above, this is hopefully fixed. Also, as per his note, the current state file cannot be used for testing.

If the author of this bug feels it has not been fixed, please let us know and we will re-open it.

Tested local client only, worked after a Reset.