Re: AIGLX
On 04/02/2011 17:14, Ken Olum wrote: From: Jon TURNEY jon.tur...@dronecode.org.uk Date: Mon, 24 Jan 2011 18:38:36 + Once I say -wgl, direct rendering no longer works. That is, if I don't set LIBGL_ALWAYS_INDIRECT, then I get a long (infinite?) sequence of errors like this: X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 73 (X_GetImage) Resource id: 0xa0039a I can't reproduce this problem. Can you give me a few more details on the host which is running paraview: unix version, version of libGL and version of paraview? Mandriva 2010.2 on x86_64 with kernel 2.6.33.7-server-2mnb libGL is from lib64mesagl1-devel-7.8.1-6mdv2010.1 Paraview is version 3.8.1 for x86 Thanks for the info. I tried to reproduce this problem using the x86 version of the above (I don't have any hardware capable of running x64 VMs at the moment), with no success, so either it's specific to x64 in some way, or there's something else I need to do. I don't have a clear picture of when this bug occurs and when it doesn't. I just deleted my paraview configuration file .config/ParaView/ParaView3.8.1.ini to start with a clean environment, and now when I type paraview it gives me a large but finite number of these warnings and then starts up. When I create objects (e.g., try Sources-Arrow) it displays them without further errors, but extremely slowly. You can watch the individual polygons appear on the screen. Do you get that error with other OpenGL applications (e.g. glxinfo) or just paraview? glxinfo does not give these errors. I haven't tried any other OpenGL application. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: AIGLX
From: Jon TURNEY jon.tur...@dronecode.org.uk Date: Mon, 24 Jan 2011 18:38:36 + Once I say -wgl, direct rendering no longer works. That is, if I don't set LIBGL_ALWAYS_INDIRECT, then I get a long (infinite?) sequence of errors like this: X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 73 (X_GetImage) Resource id: 0xa0039a I can't reproduce this problem. Can you give me a few more details on the host which is running paraview: unix version, version of libGL and version of paraview? Mandriva 2010.2 on x86_64 with kernel 2.6.33.7-server-2mnb libGL is from lib64mesagl1-devel-7.8.1-6mdv2010.1 Paraview is version 3.8.1 for x86 I don't have a clear picture of when this bug occurs and when it doesn't. I just deleted my paraview configuration file .config/ParaView/ParaView3.8.1.ini to start with a clean environment, and now when I type paraview it gives me a large but finite number of these warnings and then starts up. When I create objects (e.g., try Sources-Arrow) it displays them without further errors, but extremely slowly. You can watch the individual polygons appear on the screen. Do you get that error with other OpenGL applications (e.g. glxinfo) or just paraview? glxinfo does not give these errors. I haven't tried any other OpenGL application. Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: AIGLX
On 21/01/2011 17:52, Ken Olum wrote: From: Jon TURNEY jon.tur...@dronecode.org.uk Date: Wed, 19 Jan 2011 21:11:12 + Anyhow, can you try with 'GLWIN_NO_WGL_EXTENSIONS=1 XWin -wgl -multiwindow' Thanks. I did this and it worked. However, for a particular paraview dataset that I happened to have lying around it is slower than direct rendering by a factor of about 2. That may be related to the fact that this particular scene has wiggly tubes with structure too small to show on the screen, so there is a high ratio of data to things that actually get displayed. For the same scene, unaccelerated indirect rendering is much slower than accelerated, perhaps by a factor of 10. So when you can't use direct rendering, acceleration is a big help. Ok, thanks very much for trying it out anyhow. It's very useful to have a data point like that for an actual real-world use case :-) Another factor is possibly that you aren't going to get awesome hardware accelerated performance with an Intel 845G, either. Once I say -wgl, direct rendering no longer works. That is, if I don't set LIBGL_ALWAYS_INDIRECT, then I get a long (infinite?) sequence of errors like this: X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 73 (X_GetImage) Resource id: 0xa0039a I can't reproduce this problem. Can you give me a few more details on the host which is running paraview: unix version, version of libGL and version of paraview? Do you get that error with other OpenGL applications (e.g. glxinfo) or just paraview? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: AIGLX
From: Jon TURNEY jon.tur...@dronecode.org.uk Date: Wed, 19 Jan 2011 21:11:12 + Anyhow, can you try with 'GLWIN_NO_WGL_EXTENSIONS=1 XWin -wgl -multiwindow' Thanks. I did this and it worked. However, for a particular paraview dataset that I happened to have lying around it is slower than direct rendering by a factor of about 2. That may be related to the fact that this particular scene has wiggly tubes with structure too small to show on the screen, so there is a high ratio of data to things that actually get displayed. For the same scene, unaccelerated indirect rendering is much slower than accelerated, perhaps by a factor of 10. So when you can't use direct rendering, acceleration is a big help. Once I say -wgl, direct rendering no longer works. That is, if I don't set LIBGL_ALWAYS_INDIRECT, then I get a long (infinite?) sequence of errors like this: X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 73 (X_GetImage) Resource id: 0xa0039a I attach my XWin.0.log from a test in which I first succeeded with LIBGL_ALWAYS_INDIRECT and then got the error above without it. Ken XWin.0.log.1 Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: AIGLX
On 19/01/2011 18:53, Ken Olum wrote: From: Jon TURNEY jon.tur...@dronecode.org.uk Date: Sun, 02 Jan 2011 18:08:02 + I would suggest that for an application like ParaView, you will probably get much better performance if you use the experimental hardware accelerated OpenGL -wgl mode, see [2] for details. [2] http://cygwin.com/ml/cygwin-xfree-announce/2010-11/msg0.html I tried this, but it did not work. First I tried it in single-window mode, and that gave an error in XWin.0.log that it wouldn't work with a root window. Yes, sorry for not making that limitation clear. So then I said XWin -wgl -multiwindow, and in my XWin.0.log I have the following error: [ 8581.437] (II) AIGLX: enabled GLX_SGI_make_current_read [ 8581.437] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 8581.437] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 8581.437] (II) AIGLX: enabled GLX_SGIX_pbuffer [ 8581.437] wglGetPixelFormatAttribivARB failed for WGL_NUMBER_PIXEL_FORMATS_ARB: Unknown error (c007000d (c007000d) [ 8581.437] 0 fbConfigs [ 8581.437] pxf vis fb render Ste auxaccumMSdrawable Group/ [ 8581.437] idx ID ID VisualType Depth Lvl RGB CI DB Swap reo R G B A Z S buf AR AG AB AA bufs num W P Pb Float Trans Caveat [ 8581.437] - [ 8581.437] (II) AIGLX: Set GLX version to 1.3 [ 8581.437] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 When I try to run glx programs they don't work, and glxinfo gives me this error, regardless of whether I set LIBGL_ALWAYS_INDIRECT: Error: couldn't find RGB GLX visual or fbconfig Thanks for trying it out. I guess you win some kind of prize for being the first person to report a bug in WGL mode :-) It looks like we are failing to get a list of OpenGL visuals from the driver for your graphics card, which will prevent OpenGL from working at all. Not sure if this is due to something XWin is doing wrong or your graphics card driver not properly supporting the WGL_ARB_pixel_format extension. I wish you'd attached the full log so I could see what had been reported for GL_VERSION, GL_VENDOR and GL_RENDERER, as that would give me some idea what graphics driver causes this bug to manifest. Anyhow, can you try with 'GLWIN_NO_WGL_EXTENSIONS=1 XWin -wgl -multiwindow' which will use DescribePixelFormat() rather than the WGL_ARB_pixel_format extension and might work better? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
