Re: [Paraview] [EXTERNAL] Re: pvbatch

2017-11-16 Thread Scott, W Alan
OK, this … sort of … worked. I was able to use the Kitware download (Yay!). I called pvbatch (surprisingly, it was built by Kitware for Linux), and then used flags --mesa-llvm and --use-offscreen-rendering. I believe --use-offscreen-rendering will be replaced in the future by

Re: [Paraview] [EXTERNAL] Animation .avi output not working in v5.4.1, working in v4.4

2017-11-16 Thread Scott, W Alan
Dennis, I believe that the first line isn’t important. I believe that the second line is fatal. This is what we were seeing with 5.4.0, that I thought we fixed. Mind passing me directions to replicate (including size of the viewport, when shown in the Save Animation window, whether this is a

[Paraview] Structured meshes with Material Volume Fractions

2017-11-16 Thread Scott, W Alan
Does anyone have a very small dataset that is structured meshes, that use multiple material volume fractions? Also, are we missing a functionality processing these datsets? In other words, do we need a filter that will contour over many material volume fractions within the same filter?

[Paraview] XDMF file with multiple temporal collections

2017-11-16 Thread Nicolas Cedilnik
Hello all, I'm trying to generate a valid (at least, well-read by paraview) XDMF file. It represents a single topology/geometry, with multiple scalars, varying over time. I've attached the file I'm trying to read with paraview. It behaves almost as I want, but oddly enough, only with

[Paraview] vtkDiscreteMarchingCubes point/cell arrays from XML-PV plugin

2017-11-16 Thread Grothausmann, Roman Dr.
Dear mailing list members, Based on AcceleratedAlgorithms.xml I created an XML-PV plugin to make use of vtkDiscreteMarchingCubes (https://github.com/romangrothausmann/ParaView_XML-plugins/blob/1574430ce/vtkDiscreteMarchingCubes.xml). It basically works as expected, but does not yield any

Re: [Paraview] OpenGL inside VMWare virtual machine

2017-11-16 Thread Ben Boeckel
On Wed, Nov 15, 2017 at 11:40:43 -0500, Ken Martin wrote: > Basically there is a bug in Qt on windows where it refuses to see the 3.2 > context from Mesa because it is not a compatibility context. On startup, Qt makes a context without a profile. Mesa gives it the best compatibility profile it