Re: [PyMOL] Shader issues and automatic disabling (was Re: I just built pymol, comes up but hangs on any attempt...)

[Jason V. <jas...@sc...>]

Hi Ben,

>> 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.


The key seems to be,

>   PyMOLShader_NewFromFile-Warning: default shader files not found, loading from memory.

We load shaders from disk, but when they're not found we just read in
some basic default shaders from code, which is what this is doing. Did
you move or change $PYMOL_DATA?

Cheers,

-- Jason

-- 
Jason Vertrees, PhD
PyMOL Product Manager
Schrödinger, Inc.

(e) Jas...@sc...
(o) +1 (603) 374-7120