Hi,
Dave Partyka wrote:
Greetings Everyone,
We have just made ParaView 3.8.0 Release Candidate 1 binaries
available for download on the ParaView download page. Final binaries
and/or more release candidates should follow shortly after the Git
transition occurring next week.
When you configure manta, try turning MANTA_SSE off.
Then run manta to make sure that manta itself is working.
Then rebuild paraview and try the manta plugin.
You may want to ping the manta mailing list about why SSE isn't found
on your platform and why that code path in DynBVH fails when it
Dave Partyka wrote:
Greetings Everyone,
We have just made ParaView 3.8.0 Release Candidate 1 binaries
available for download on the ParaView download page. Final binaries
and/or more release candidates should follow shortly after the Git
transition occurring next week.
Hi David,
David E DeMarle wrote:
When you configure manta, try turning MANTA_SSE off.
Right, that's what my next step turned out to be :)
Costs a lot of performance though... (8.7 fps instead 18 for the
standard manta demo).
Then rebuild paraview and try the manta plugin.
You may want to
David E DeMarle wrote:
When you configure manta, try turning MANTA_SSE off.
Then run manta to make sure that manta itself is working.
By the way, on a Vis09 presentation by Jon Woodrig, yourself and others
it is mentioned that you should configure manta with MANTA_USE_X11 to
OFF. Is that
As far as I know you don't _need_ to turn off X11 in manta to use it
in ParaView - I never do. Although I can think of reasons why it
_might_ make sense to do so I am not really sure why we made that
recommendation back then.
Thanks for the detailed report on the SSE config. I will fix that.
I have PARAVIEW_ENABLE_PYTHON to OFF (the default it seems as I didn't
touch it) and get this compile error with PV 3.8rc1:
Paul, you are correct, the plugin should not be built if
PARAVIEW_ENABLE_PYTHON is OFF. Dave, can we make sure that the plugin
in OFF if PARAVIEW_ENABLE_PYTHON is OFF? One
Will do.
On Fri, Apr 16, 2010 at 10:04 AM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
I have PARAVIEW_ENABLE_PYTHON to OFF (the default it seems as I didn't
touch it) and get this compile error with PV 3.8rc1:
Paul, you are correct, the plugin should not be built if
David E DeMarle wrote:
As far as I know you don't _need_ to turn off X11 in manta to use it
in ParaView - I never do. Although I can think of reasons why it
_might_ make sense to do so I am not really sure why we made that
recommendation back then.
Well, I finally got the plugin to work
I would be in favor of the reverse where plugins aren't available as an
option unless building as shared.
On Fri, Apr 16, 2010 at 10:23 AM, Paul Melis paul.me...@sara.nl wrote:
David E DeMarle wrote:
As far as I know you don't _need_ to turn off X11 in manta to use it
in ParaView - I never
Is that still under the ParaView-3-8 CVS tag?
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On Apr 15, 2010, at 1:34
Another option would be to print a message if any plugin is enabled
and shared libraries if OFF. It's perfectly legal to build static
plugins to be included into static applications.
Utkarsh
On Fri, Apr 16, 2010 at 10:30 AM, Dave Partyka dave.part...@kitware.com wrote:
I would be in favor of
I noticed there was a separate window showing the manta output a second
time, but that probably isn't caused by the X11 setting?
Yes, that isn't related to X11, it is part of the way vtkManta works
in ParaView and a proper fix is on my long term goal list. In the
meantime, you can get around it
13 matches
Mail list logo
