View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007789ParaView(No Category)public2008-10-07 21:322009-05-13 13:59
ReporterAlan Scott 
Assigned ToUtkarsh Ayachit 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version3.4Fixed in Version3.4 
Summary0007789: D3 is broken with opacity not 1
DescriptionThis needs to go into ParaView 3.4.2

Run ParaView client/server. I am using 4 servers.

Open disk_out_ref.exo. I am coloring by Temp, but it shouldn't matter.

Filter D3, Divide Cells. Apply.
Change opacity to 0.50. Touch the main window, for instance rotating the object slightly. The object totally disappears.

I tried volume rendering, but it took so long I gave up. Probably killed the server.
TagsNo tags attached.
Project
Topic Name
Type
Attached Files

 Relationships

  Notes
(0014088)
Alan Scott (manager)
2008-11-11 21:02

I tried changing the opacity from 1 to 0.5 using mesa and 12 pvservers. As I rtotated it, it quickly hung. I tried with 4 servers, and it seemed OK.

So, to replicate this, try using more servers.
(0014089)
Alan Scott (manager)
2008-11-11 21:05

Sorry, forgot to mention this is on the ParaView trunk.
(0014124)
Utkarsh Ayachit (administrator)
2008-11-17 09:36

This should now be fix. There were issues with updates when OrderedCompositing was employed which resulted in deadlocks. Tested with 12 servers and seems to work for me now.
(0014171)
Alan Scott (manager)
2008-11-24 21:59

This now works - sort of.

Do as listed below. Then, change opacity back to 1.0. The object will get really strange - opaque. Click off the Interpolate Colors button, all is now normal, click on the Interpolate Colors button, all is still normal.
(0014176)
Utkarsh Ayachit (administrator)
2008-11-25 09:47

The check to use previously generated texture did not take into
consideration if the last-used-opacity was different than the current one
explicitly. It relied on it being different from the opacity of the LUT, which
worked in most cases but failed in some. eg. change opacity to something
(say .5) and then back to 1.0. Fixed that.

/cvsroot/ParaView3/ParaView3/VTK/Rendering/vtkScalarsToColorsPainter.cxx,v <-- VTK/Rendering/vtkScalarsToColorsPainter.cxx
new revision: 1.17; previous revision: 1.16
(0014298)
Alan Scott (manager)
2008-12-04 22:05

Tested client/server. Looks good!

 Issue History
Date Modified Username Field Change
2008-10-07 21:32 Alan Scott New Issue
2008-10-07 21:33 Alan Scott Status backlog => tabled
2008-10-07 21:33 Alan Scott Assigned To => Utkarsh Ayachit
2008-11-11 21:02 Alan Scott Note Added: 0014088
2008-11-11 21:05 Alan Scott Note Added: 0014089
2008-11-17 09:36 Utkarsh Ayachit Note Added: 0014124
2008-11-17 09:36 Utkarsh Ayachit Status tabled => @80@
2008-11-17 09:36 Utkarsh Ayachit Resolution open => fixed
2008-11-24 21:59 Alan Scott Note Added: 0014171
2008-11-24 21:59 Alan Scott Status @80@ => @20@
2008-11-24 21:59 Alan Scott Resolution fixed => reopened
2008-11-25 09:47 Utkarsh Ayachit Note Added: 0014176
2008-11-25 09:47 Utkarsh Ayachit Status @20@ => @80@
2008-11-25 09:47 Utkarsh Ayachit Resolution reopened => fixed
2008-12-04 22:05 Alan Scott Note Added: 0014298
2008-12-04 22:05 Alan Scott Status @80@ => closed
2009-05-13 13:58 Utkarsh Ayachit Target Version => 3.4
2009-05-13 13:59 Utkarsh Ayachit Fixed in Version => 3.4
2011-06-16 13:10 Zack Galbreath Category => (No Category)


Copyright © 2000 - 2018 MantisBT Team