Alaghast

Hi shader jitter ninjas, i'm little bit in confusion about the relationship of texcoord and texdim inside max/msp. Someone could clarify a little bit what these two do in a generic GLSL context?

For instance: texcoord0 is like gl_FragCoord.st? 

Texdim0 is something like a "resolution".xy of texture/matrix considered in the first inlet of a jit.gl.slab?

Inside the jit.gl.slab, these two are considered in pixel or normalized values?

If you take the repos.jxs file example you can see that inside jit.gl.slab the shader has the texdim0 built in variable and inside the jit.gen repos.genjit example it doesn't have any.

Hi shader jitter ninjas, i'm little bit in confusion about the relationship of texcoord and texdim inside max/msp. Someone could clarify a little bit what these two do in a generic GLSL context? 

For instance: texcoord0 is like gl_FragCoord.st? 
Texdim0 is something like a "resolution".xy of texture/matrix considered in the first inlet of a jit.gl.slab? 

Inside the jit.gl.slab, these two are considered in pixel or normalized values? 

If you take the repos.jxs file example you can see that inside jit.gl.slab the shader has the texdim0 built in variable and inside the jit.gen repos.genjit example it doesn't have any. 

Hi shader jitter ninjas, i'm little bit in confusion about the relationship of texcoord and texdim inside max/msp. Someone could clarify a l

texcoord and texdim behaviours