On 9/10/11 10:23 AM, Kevin Van Workum wrote: > In my TurboVNC display (:1) I see the when running my app (VMD): > > ERROR) The X server does not support the OpenGL GLX extension. Exiting ... > Info) Unable to create OpenGL window. > > "glxinfo -display :0" reports: > direct rendering: No > > glxinfo -display :1 says: > Xlib: extension "GLX" missing on display ":1.0". > Error: couldn't find RGB GLX visual > > and "vglrun -d :0 glxinfo -display :1" complained: > Error: couldn't find RGB GLX visual > > which makes sense since I don't have Pbuffer support. > > But still can't get my OpenGL to work on TurboVNC using your suggestions.
I can't either. Tried on RHEL 5 (Mesa 6.5.1) and RHEL 6 (Mesa 7.10). Now that I think about it, how could setting LIBGL_ALWAYS_INDIRECT=1 possibly work? That's forcing Mesa to use indirect OpenGL rendering, which requires that the X server have a GLX extension (which TurboVNC doesn't.) You might be able to use the undocumented and unsupported "render to window" feature in VirtualGL, activated by setting VGL_WINDOW=1 in the environment. This feature is used only for internal testing, and it probably won't produce correct results if you have multiple 3D windows in the application or multiple application instances. ------------------------------------------------------------------------------ Malware Security Report: Protecting Your Business, Customers, and the Bottom Line. Protect your business and customers by understanding the threat from malware and how it can impact your online business. http://www.accelacomm.com/jaw/sfnl/114/51427462/ _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
