MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012244ParaViewBugpublic2011-06-03 18:282016-08-12 09:58
ReporterBurlen 
Assigned ToUtkarsh Ayachit 
PrioritynormalSeveritymajorReproducibilitysometimes
StatusclosedResolutionmoved 
PlatformTACC LonghornOSOS Version
Product Version3.10 
Target VersionFixed in Version 
Project
Topic Name
Type
Summary0012244: screen partially trashed after resize
DescriptionOn Longhorn (GPU rendering) visualizing a 2d dataset that has a large ratio (w/h) I am seeing that about 5-20% of the width of the view (slice, surface, or LIC representation) is cut off on the right side. This cut off area still takes on the background color until the window is resized at which point the area becomes trashed (attached screen shot). The size of the affected area seems to a be a function of the window aspect ratio.It happens whether I use 1 process or more.

Steps To Reproduceopen data
resize screen
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng slice_bug_20%.png (709,518) 2011-06-03 18:28
https://www.vtk.org/Bug/file/8910/slice_bug_20%25.png
png lic_bug_20%.png (910,048) 2011-06-06 15:45
https://www.vtk.org/Bug/file/8914/lic_bug_20%25.png
Issue History
Date ModifiedUsernameFieldChange
2011-06-03 18:28BurlenNew Issue
2011-06-03 18:28BurlenFile Added: slice_bug_20%.png
2011-06-06 12:37Utkarsh AyachitNote Added: 0026674
2011-06-06 13:53BurlenNote Added: 0026675
2011-06-06 13:56Utkarsh AyachitNote Added: 0026676
2011-06-06 15:43BurlenNote Added: 0026678
2011-06-06 15:45BurlenFile Added: lic_bug_20%.png
2011-06-06 15:46BurlenNote Added: 0026679
2011-06-06 15:46BurlenNote Edited: 0026679bug_revision_view_page.php?bugnote_id=26679#r344
2011-10-07 13:29BurlenNote Added: 0027546
2011-10-10 12:17Utkarsh AyachitNote Added: 0027558
2011-10-10 12:17Utkarsh AyachitStatusbacklog => closed
2011-10-10 12:17Utkarsh AyachitAssigned To => Utkarsh Ayachit
2011-10-10 12:17Utkarsh AyachitResolutionopen => suspended
2011-10-10 12:18Utkarsh AyachitNote Added: 0027559
2011-10-10 12:18Utkarsh AyachitStatusclosed => backlog
2011-10-10 12:18Utkarsh AyachitResolutionsuspended => reopened
2015-01-02 10:43Utkarsh AyachitFixed in Version => 4.3
2016-08-12 09:58Kitware RobotNote Added: 0037981
2016-08-12 09:58Kitware RobotStatusbacklog => closed
2016-08-12 09:58Kitware RobotFixed in Version4.3 =>
2016-08-12 09:58Kitware RobotResolutionreopened => moved

Notes
(0026674)
Utkarsh Ayachit   
2011-06-06 12:37   
On longhorn, I am assuming you are not using mesa. In that case any time you are asking OpenGL to create a buffer of size larger than the actual display, you'll have issues. Do you think that's what you are seeing here?
(0026675)
Burlen   
2011-06-06 13:53   
I am using nvidia driver's opengl.

I think you may be onto something here, the remote display is (1280x1024) while my desktop display is (1900x1280) so it is easy for me to exceed the remote display size.

Is this something PV should handle gracefully?
(0026676)
Utkarsh Ayachit   
2011-06-06 13:56   
Try running pvserver with --use-offscreen-rendering. It uses FBOs, if available and then the OpenGL/screen size restrictions don't seem to have effect. Of course it will still your hardware acceleration, so nothing should change in that respect.

Does that help?
(0026678)
Burlen   
2011-06-06 15:43   
Using offscreen helps for the surface and slice rep. But when using the LIC rep. the screen still gets trashed, in the same way.
(0026679)
Burlen   
2011-06-06 15:46   
added a screenshot of the LIC rep using offscreen rendering.
(0027546)
Burlen   
2011-10-07 13:29   
A work around is to configure the server side display with a high resolution such as 2550x1920,a common resolution for a 30" monitor. most users won't exceed this.
(0027558)
Utkarsh Ayachit   
2011-10-10 12:17   
Will reopen if this starts becoming a major problem for customers.
(0027559)
Utkarsh Ayachit   
2011-10-10 12:18   
Umm, I changed my mind. Leaving this open for now. Let's see what we can do.
(0037981)
Kitware Robot   
2016-08-12 09:58   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.