[Xquartz-dev] 2.3.3_rc1

[Jeremy Huddleston]

We don't intend to support indirect rendering with the new libGL in  
the short term.  It's really too slow and only useful when the X  
client is on a remote system (which is rarely the case for OSX apps).   
Are you running vmd-xplor on a remote system for some reason?  If that  
were the case, then I'd expect glxinfo to actually bail with an  
AppleDRI error.

--Jeremy

On Mar 9, 2009, at 17:13, Jack Howarth wrote:

> George,
>   I believe I have figured out the origin of the problems
> with vmd-xplor on 2.3.3-rc1. The problem is that the new
> GLX/DRI code doesn't honor LIBGL_ALWAYS_INDIRECT when it
> is set. Under X11 2.3.2.1, I get...
>
> [Macintosh-2:~] howarth% setenv LIBGL_ALWAYS_INDIRECT 1
> [Macintosh-2:~] howarth% glxinfo | grep direct
> direct rendering: No (LIBGL_ALWAYS_INDIRECT set)
>
> whereas under 2.3.3-rc1, I get...
>
> [Macintosh-2:~] howarth% setenv LIBGL_ALWAYS_INDIRECT 1
> [Macintosh-2:~] howarth% glxinfo | grep direct
> Xlib:  extension "Generic Event Extension" missing on display "/tmp/ 
> launch-W4Xpc5/:0".
> Xlib:  extension "Generic Event Extension" missing on display "/tmp/ 
> launch-W4Xpc5/:0".
> direct rendering: Yes
>
> If you can fix this in the GLX, I can test it to see if this
> eliminates the issues with vmd-xplor on the HD2600.
>                 Jack
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev