Hi Jason, > If your machine does have shader issues and they don't automatically > disable, please let us know.
What would be the symptoms/output if this is happening? I get occasional reports from our users with errors like this: CShaderPrg_New-Error: vertex shader compilation failed name='default'; log follows. infoLog=cI PyMOLShader_NewFromFile-Warning: default shader files not found, loading from memory. CShaderPrg_Link-Error: Shader program failed to link name='default'; GL_MAX_VARYING_FLOATS=124 log follows. $^? CShaderPrg_New-Error: vertex shader compilation failed name='volume'; log follows. They seem to be informational, since PyMOL seeems to run reasonably well even after outputting those messages, but I can't say for sure. The graphics start up message on the machine looks pretty normal to me: Detected GLSL version 1.20. OpenGL graphics engine: GL_VENDOR: NVIDIA Corporation GL_RENDERER: Quadro 4000/PCIe/SSE2 GL_VERSION: 2.1.2 NVIDIA 304.37 Adapting to Quadro hardware. Detected 24 CPU cores. Enabled multithreaded rendering. -ben -- | Ben Eisenbraun | SBGrid Consortium | http://sbgrid.org | | Harvard Medical School | http://hms.harvard.edu | ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net) Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net
