<div dir="ltr">Forgot to post the link to the bug I created on Mantis<br><br><a href="http://www.vtk.org/Bug/view.php?id=7606">http://www.vtk.org/Bug/view.php?id=7606</a><br><br><div class="gmail_quote">On Thu, Sep 4, 2008 at 2:33 PM, Berk Geveci <span dir="ltr"><<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If you have PV_PLUGIN_PATH defined on the server, ParaView should load<br>
plugins from it. If this does not work, please report a bug in the<br>
tracker.<br>
<br>
-berk<br>
<div><div></div><div class="Wj3C7c"><br>
On Fri, Aug 29, 2008 at 2:45 PM, Chris Cameron<br>
<<a href="mailto:heyitschriscameron@gmail.com">heyitschriscameron@gmail.com</a>> wrote:<br>
> Hello,<br>
><br>
> When I use paraview built-in or client-server mode, PV_PLUGIN_PATH points to<br>
> a folder that has all of my Server and Client plugins. When I open the<br>
> paraview client, my server and client plugins have all been automatically<br>
> loaded.<br>
><br>
> When I use paraview MPI however, only the client plugins are loaded<br>
> automatically. I must load the server plugins manually.<br>
><br>
> What environment variable should be used to load remote server plugins in<br>
> MPI?<br>
><br>
> --<br>
> Chris Cameron<br>
> Mirarco Mining Innovation - e2vo<br>
> 705-675-1151<br>
> x5113<br>
><br>
</div></div>> _______________________________________________<br>
> ParaView mailing list<br>
> <a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
><br>
><br>
</blockquote></div><br><br clear="all"><br>-- <br>Chris Cameron<br>Mirarco Mining Innovation - e2vo<br>705-675-1151<br>x5113 <br>
</div>