[enabling] compositing on ParaView 3.0.2 on purple (Lawrence Livermore AIX 100 TFLOP monster!) causes black render window
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
This bug manifests when running 3.0.2 (server) on purple. The client render window comes up black by default (because compositing is enabled). Creating a source, e.g. a cone, works, but you don't see anything in the window until compositing is disabled in the server tab of the Settings dialog.
-- The build for purple was done on uP, the unclassified version of the machine, and the binaries transferred to the classified purple, so there could be issues. I will do a build directly on purple itself.
-- ParaView3's interactive rate can be very slow, to the point of unusable. I ran with one purple node, loaded a data set that had 32 files, about 184K cells, 287K points, 41 MB memory footprint (according to the statistics view). Maybe this is related to the compositing issue...? Or maybe it's just taking a long time to transfer the the initial geometry data from purple to Sandia. But then after everthing is loaded and the geometry is present, doing things like loading can.ex2, along with the 32-file data set, and interacting with the models - turning eyeballs on/off, rotating camera, etc.) can cause slowdowns and some erratic rendering behaviour (lines show up in middle of screen, random rectangles, which go away after rotating the model or eyeballing again.
-- Sometimes the data did not show after loading. Again, with the 32 data set from above, I had to click the eyeball off, then on again for anything to appear in the render window. I thought the app had crashed or hung.