-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
i thought it might be a good idea to inform you:
glsl_ objects now stopped emitting the shader-IDs for each and every frame. instead, the shaderID is emitted only once, when the shaders are loaded. thus you won't need the [change] object anymore, to prevent [glsl_program] to link a new program for each frame.
caveat: currently only valid shaders are sent; if linking fails, you don't know (should be (if needed): 0)
fgamsdr IOhannes
Le 14/02/2011 10:23, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
i thought it might be a good idea to inform you:
glsl_ objects now stopped emitting the shader-IDs for each and every frame.
nice
instead, the shaderID is emitted only once, when the shaders are loaded. thus you won't need the [change] object anymore, to prevent [glsl_program] to link a new program for each frame.
caveat: currently only valid shaders are sent; if linking fails, you don't know (should be (if needed): 0)
if it fail, there is an error in pd log. I think it's ok.
thanks c
fgamsdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1Y9JIACgkQkX2Xpv6ydvR5qwCdGswUxLOAoXpBokLqDQbZmDAO A3kAoLMjtN8KoHbQ+AuCTwQp+cm1XlYQ =0OXa -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Yep, good new ! ++
Jack
Le lundi 14 février 2011 à 12:12 +0100, cyrille henry a écrit :
Le 14/02/2011 10:23, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
i thought it might be a good idea to inform you:
glsl_ objects now stopped emitting the shader-IDs for each and every frame.
nice
instead, the shaderID is emitted only once, when the shaders are loaded. thus you won't need the [change] object anymore, to prevent [glsl_program] to link a new program for each frame.
caveat: currently only valid shaders are sent; if linking fails, you don't know (should be (if needed): 0)
if it fail, there is an error in pd log. I think it's ok.
thanks c
fgamsdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1Y9JIACgkQkX2Xpv6ydvR5qwCdGswUxLOAoXpBokLqDQbZmDAO A3kAoLMjtN8KoHbQ+AuCTwQp+cm1XlYQ =0OXa -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-02-14 12:12, cyrille henry wrote:
caveat: currently only valid shaders are sent; if linking fails, you don't know (should be (if needed): 0)
if it fail, there is an error in pd log. I think it's ok.
that's why it is not high on my todo list :-)
generally i think it's nicer if you get feedback in the patch as well, so you can programmatically react on it...
fgmasdr IOhannes
On 02/14/2011 12:26 PM, IOhannes m zmoelnig wrote:
if it fail, there is an error in pd log. I think it's ok.
that's why it is not high on my todo list :-)
generally i think it's nicer if you get feedback in the patch as well, so you can programmatically react on it...
Yes, it is very important to be able to react to any error programmatically!
-
cyrille henry -
IOhannes m zmoelnig -
Jack -
Matteo Sisti Sette