On Mon, Jan 02, 2017 at 21:36:51 +0100, Fabian Wein wrote:
> Then I do something wrong:
>
> cmake ../paraview-superbuild -DCMAKE_BUILD_TYPE:STRING=Release
> -DBUILD_TESTING=OFF -DENABLE_cxx11=ON -DENABLE_qt5=ON -DENABLE_boost:BOOL=ON
> -DENABLE_hdf5:BOOL=ON -DENABLE_zlib:BOOL=ON
Then I do something wrong:
cmake ../paraview-superbuild -DCMAKE_BUILD_TYPE:STRING=Release
-DBUILD_TESTING=OFF -DENABLE_cxx11=ON -DENABLE_qt5=ON -DENABLE_boost:BOOL=ON
-DENABLE_hdf5:BOOL=ON -DENABLE_zlib:BOOL=ON -DENABLE_png:BOOL=ON
Glyph with Custom source filter can do it. Note that it works in CPU/RAM
instead of in a GPU shader so memory can be an issue for all the replicated
geometry.
To use it, manufacture a mesh that appears the way you want it and save it
in a common mesh format. Load that into the pipeline and hide
On Fri, Dec 30, 2016 at 23:48:52 +0100, Fabian Wein wrote:
> • enable_paraviewexternalplugins:BOOL=ON: Enables building using external
> plugins.
Sorry, that should be ENABLE_paraviewexternalplugins. PR pushed:
https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/253
Hi Debopam,
Do you see the orientation axis? Does it move when you rotate the scene?
What happen when you click on "+" and choose the Wavelet? Do you see
something?
I'm wondering if you still run into an invalid path issue due to / or \.
Seb
On Mon, Jan 2, 2017 at 6:38 AM, Debopam Ghoshal
Hi Ufuk,
I'm not sure what is causing the difference. I'm guessing not all of the
information for the view is saved in the state. Any chance that you're
using different versions of ParaView for the GUI and Catalyst generated
images? I see that the Python script is specifying that it was generated
Hi,
The Catalyst examples have been moved to the ParaView source repo. I'd
recommend using the newest version of ParaView as well as Catalyst since
there have been a lot of improvements since PV 4.4.
For the CxxFullExample, if you've built it with Catalyst enabled you can
run it as you've done
Hi Seb,
1. "C:/ParaView-5.2.0-Qt4-OpenGL2-MPI-Windows-64bit/data" works fine. Now
we can see the list of files in the data folder.
However, there seems to be some problem with the ParaviewWeb Application
(or may be with the graphics driver?). Because we cannot render the sample
mesh files (eg: