Bishwajit,
Just remove the "SetScaleArray" invocation from your script to over
this issue. I suspect you're building the GUI with
VTK_RENDERING_BACKEND cmake variable set to OpenGL2, while with 5.0.1,
it may be defaulting to OpenGL, as a result your Mesa build is using
legacy OpenGL backend. This
Jose,
It looks like the file for time step 50 is incomplete: there is less values
than expected.
See, the files correspond to same mesh, only the "roh" point array is
different but file t50
is more than 6MB smaller than t0 which is not correct as data is written in
binary but not
compressed. So I
Not sure if it is a general Gmsh reader, but there is a merge request
pending that claims to introduce a reader.
https://gitlab.kitware.com/paraview/paraview/merge_requests/1453
On Mon, Apr 3, 2017 at 3:39 PM, Cory Quammen
wrote:
> Zach,
>
> Thanks for trying it
Dear ParaView experts,
I managed to get ParaView 5.2.0 running in our Cave. I connect a cluster of
servers, load the VR plugin, connect VRPN and start tracking. Then I load one
of the geometric primitives like a cube and I am glad to say that I see the
object moving when moving the glasses, so
Bruce,
Thanks for the report, and sorry for the inconvenience. Cleaning up
the Point Gaussian representation is being tracked in an issue here:
https://gitlab.kitware.com/paraview/paraview/issues/17000
Best,
Cory
On Tue, Apr 4, 2017 at 8:32 AM, Bruce Jones wrote:
Colleagues,
Is there any ETA for incorporating this, or similar, functionality to
disable the log warning when zero/negative values are encountered?
https://gitlab.kitware.com/paraview/paraview/merge_requests/827
Please contact me with any comments, questions, or concerns.
Thank you,
Joel
When using Point Gaussian for a large number of points, with an unsuitably
large Gaussian radius, ParaView becomes unresponsive for a long time before
it finally renders. In ParaView <=5.2, this was a fairly minor annoyance,
the default Gaussian radius was always too high, but you could set the
Cory,
Thank you for response. Bil has already solved it (crashing problem, on
January 25th, 2017) and pushed it to repository, so it became part of
ParaView v5.3.0 release.
Thanks,
Nenad.
On Tue, Apr 4, 2017 at 2:44 AM, Cory Quammen
wrote:
> Nenad,
>
> Sorry, this