[Paraview] PV 3.6.2 and VirtualGL

Utkarsh Ayachit utkarsh.ayachit at kitware.com
Wed Mar 3 09:16:56 EST 2010


That's very interesting. You are seeing the issue only with glyph not
with any other filter? I am wondering if you can show two 3D
geometries at the same time and does that work?

On Wed, Mar 3, 2010 at 7:27 AM, Paul Melis <paul.melis at sara.nl> wrote:
> Hi,
>
> I'm experimenting with running paraview on a remote visualization
> server, using VirtualGL. This package basically lets you run an OpenGL
> application as you normally would, but intercepts the swapbuffer events
> to read back the framebuffer, which then gets JPEG compressed and sent
> to a client machine (see [1] for an excerpt from the manual). On the
> client side you get a normal X11 application (using X forwarding), but
> the 3D rendering is done on the server side and transported using a
> dedicated connection.
>
> When using PV 3.6.2 in this setup I get the following strange results. I
> have a dataset on which I apply the Glyph filter. When running PV
> locally (without any remote rendering) this glyphing works fine. But,
> when I run paraview remotely it refuses to show glyphs for the exact
> same dataset and same pipeline. The strange thing is that I can't get
> any of the glyph types to show anything, except for 2D Glyph + Vertex.
> For that mode I get what I expect.
>
> I've disabled depth peeling to exclude a source of possible
> interference. VirtualGL itself should basically leave the 3D rendering
> untouched, except during context creation and on swapbuffer events. Is
> there anything special in how Paraview draws its glyphs?
>
> Thanks,
> Paul
>
>
> [1] "Whenever a window is created by the application, VirtualGL creates
> a corresponding 3D pixel buffer (“Pbuffer”) on a 3D graphics card in the
> application server. Whenever the application requests that an OpenGL
> rendering context be created for the window, VirtualGL intercepts the
> request and creates the context on the corresponding Pbuffer instead.
> Whenever the application swaps or flushes the drawing buffer to indicate
> that it has finished rendering a frame, VirtualGL reads back the Pbuffer
> and sends the rendered 3D image to the client."
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>


More information about the ParaView mailing list