Hi Jason,
We read the shaders from $PYMOL_PATH/data/shaders. We should be
reading them from $PYMOL_DATA/shaders. If you'd like to change this on
your own compiled PyMOL you'll need to change lines 411 and 418 of
pymol/layer0/ShaderMgr.c and rebuild. If you're a paying PyMOL
subscriber this
Hi Ben,
We read the shaders from $PYMOL_PATH/data/shaders. We should be
reading them from $PYMOL_DATA/shaders. If you'd like to change this on
your own compiled PyMOL you'll need to change lines 411 and 418 of
pymol/layer0/ShaderMgr.c and rebuild. If you're a paying PyMOL
subscriber this should
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
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
Hi Jason,
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
Ben,
Ah, I bet this is because they are running it via X-forwarding over an
ssh tunnel. I'm pretty certain that one of the reports came from a user
running PyMOL this way, and I can duplicate the error messages running over
a tunnel.
Is this actually going to break anything?
Yes -- volumes
Hi Jason,
Ah, I bet this is because they are running it via X-forwarding over an
ssh tunnel. I'm pretty certain that one of the reports came from a user
running PyMOL this way, and I can duplicate the error messages running over
a tunnel.
Is this actually going to break anything?
