cyrille henry wrote:
this is because [pix_info] will output information on the "pix" (that is: image-data in main memory) in the gemchain. since you don't have a "pix" in the chain, you get invalid data.
and it's the same information that are used by the shader coordinate. so shader does have invalid data...
no, why should this information be used by the shader-coordinate? (i haven't had a look at all the patches in this thread yet; probably one of the patches _does_ use the output of [pix_info] to scale some parameter; but the shader-objects themselves do not know anything about the "pix" data (e.g. the width/height as read by [pix_info]) - instead they have this data available in a more abstract way (on the openGL side))
(or the like, i don't remember the arguments of the texture-message by heart, just print them to see what you are doing)
i just noticed that [gemframebuffer] does not output the full information for the pix_texture; this should be fixed, though it shouldn't be a problem here.
the frambuffer output is correct, but it look like pix_texture does not use this infos.
hmm, it seems like your patch is working fine here. (the tex-info of the framebuffer is ok, [pix_texture] seems to respect it)
probably i should have a look at a patch where the problem is really exposed.
(and i should add better aliases for the messages to [gemframebuffer]; like "dimen" instead of "dim", and "rectangle" instead of "mode" to make it in-line with other objects...)
gmart IOhannes