|
Notes |
|
|
(0014088)
|
|
Alan Scott
|
|
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
|
|
2008-11-11 21:05
|
|
|
Sorry, forgot to mention this is on the ParaView trunk. |
|
|
|
(0014124)
|
|
Utkarsh Ayachit
|
|
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
|
|
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
|
|
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
|
|
2008-12-04 22:05
|
|
|
Tested client/server. Looks good! |
|