Hi,

just to round this thread up:

The problem with the limited screen (the ungarbled output is VGA 640x480) can 
be resolved by
using offscreen rendering, so I guess this is somewhat related to the graphics 
card, though the
connection information still shows the nvidia card being used in that case.

However, there are two systems where the complete screen is garbled. Even when 
using
offscreen rendering on the pvserver side. For those I needed to fallback to 
x2go and VirtualGL,
and I am now using the precompiled binaries. Those do not exhibit the 
segmentation fault that
I observed with the self-compiled version. The main difference seems to be the 
usage of Qt5.

Thus, I guess the formerly observed segfault is related to some interaction 
between Qt5 and the
OpenGL2 rendering.

Best,
Harald

> Am 13.04.2016 um 12:44 schrieb Harald Klimach <[email protected]>:
> 
> The X+OpenGL2 via pvserver works fine for me now.
> However, my colleagues with older local laptops do have some trouble.
> 
> My local system uses:
> OpenGL Version 4.1 INTEL-10.6.33
> OpenGL Renderer Intel Iris Graphics 6100
> 
> This works nicely.
> 
> With an older graphics card like:
> OpenGL Version 3.3 INTEL-10.0.40
> OpenGL Renderer Intel HD Graphics 3000 OpenGL Engine
> 
> There is only a small 3D screen section that is actually usable, the rest of 
> the screen has garbled output.
> The Legend can be displayed correctly on top of the garbled 3D content, and 
> when rotating or moving the
> geometry also the complete scenery is correctly shown. As soon as the 3D 
> scenery is still, there are
> parts of the screen garbled.
> 
> When going back to the legacy OpenGL backend on the server, both kinds of 
> clients
> die when trying to render a 3D object.
> 
>> Am 12.04.2016 um 22:42 schrieb Harald Klimach <[email protected]>:
>> 
>>> Unfortunately I suspect this is an issue with NVIDIA driver. Their EGL 
>>> support is still brand new and currently seems to be fairly brittle between 
>>> driver releases so perhaps best to wait until it settles a bit and just 
>>> stick with X for now :-(.  Are you able to use the X+OpenGL2 (i.e. no egl)  
>>> pvserver for remote rendering?
>> 
>> Yes, as reported in http://paraview.markmail.org/thread/c46ycyk3db4spov4, 
>> this
>> option seems to work. One weird thing I observed is the different OpenGL 
>> version
>> strings reported when using OpenGL2+EGL.
>> 
>> X+OpenGL2 is perfectly fine, I’ll test this a little more extensively.
>> Thanks a lot for bearing with me!
>> 
>> Harald
>> _______________________________________________
>> 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
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
> 
> _______________________________________________
> 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
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

_______________________________________________
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Reply via email to