AdamW

I want to apply a .jxs shader to an OpenGl geometry I generate in a lua script, but I'm not sure how to approach it. Is it even possible?

I want to apply a .jxs shader to an OpenGl geometry I generate in a lua script, but I'm not sure how to approach it. Is it even possible?
Something like this:

function draw()
 --Apply shader.jxs?
   gl.PushMatrix()
   gl.Begin("QUADS") 
     gl.Vertex(-1., 0, 0) 
     gl.Vertex(1., 0, 0)
     gl.Vertex(1., 1., 0)
     gl.Vertex(-1., 1., 0) 
   gl.End()
   gl.PopMatrix()
end

jxs-shaders-in-jit-gl-lua

3. bind the output of the slab onto the geometry

tex = jit.new("jit.gl.texture", this.drawto)

slab = jit.new("jit.gl.slab", this.drawto)

another way would be to draw the geometry in between jit.gl.begincapture("foo") and jit.gl.endcapture("foo"), then make a jit.gl.texture in jitter with @name foo. this way you have your slab in jitter and the geometry in lua.

hope this helps, still discovering lua here.

hi, I would try it this way:
1. create a texture
2. create a slab
3. bind the output of the slab onto the geometry

tex = jit.new("jit.gl.texture", this.drawto)
tex.file = texture.jpg

slab = jit.new("jit.gl.slab", this.drawto)
slab.texture = tex
slab.file = co.normal.jxs

gl.Begin("QUADS")
--top left
gl.TexCoord(0., 1.)
gl.Vertex(-0.5, 0.5, 0.)

--bottom left
gl.TexCoord(0., 0.)
gl.Vertex(-0.5, -0.5, 0.)

--bottom right
gl.TexCoord(1., 0.)
gl.Vertex(0.5, -0.5, 0.)

--top right
gl.TexCoord(1., 1.)
gl.Vertex(0.5, 0.5, 0.)	
gl.End()

another way would be to draw the geometry in between jit.gl.begincapture("foo") and jit.gl.endcapture("foo"), then make a jit.gl.texture in jitter with @name foo. this way you have your slab in jitter and the geometry in lua.
hope this helps, still discovering lua here.
erik


This is how you use shaders. You just make a shader object and call

shader = jit.new("jit.gl.shader", this.drawto)

shader.file = "cc.brcosa.jxs" --shader file to load

This is how you use shaders.  You just make a shader object and call
its bind methods.
wes

shader = jit.new("jit.gl.shader", this.drawto)
shader.file = "cc.brcosa.jxs" --shader file to load

gl.Begin("QUADS")
 --top left
gl.TexCoord(0., 1.)
gl.Vertex(-0.5, 0.5, 0.)

--top right
gl.TexCoord(1., 1.)
gl.Vertex(0.5, 0.5, 0.)
gl.End()

I'm not around my computer to try it, but are multiple bindings 

On Feb 3, 2008, at 1:24 PM, "Wesley Smith" 

> This is how you use shaders. You just make a shader object and call

> shader = jit.new("jit.gl.shader", this.drawto)

> shader.file = "cc.brcosa.jxs" --shader file to load

I'm not around my computer to try it, but are multiple bindings  
available?

On Feb 3, 2008, at 1:24 PM, "Wesley Smith"   
wrote:

> This is how you use shaders.  You just make a shader object and call
> its bind methods.
> wes
>
>
> shader = jit.new("jit.gl.shader", this.drawto)
> shader.file = "cc.brcosa.jxs" --shader file to load
>
> function draw()
>
>
> shader:bind()
>
> gl.Begin("QUADS")
> --top left
> gl.TexCoord(0., 1.)
> gl.Vertex(-0.5, 0.5, 0.)
>
> --bottom left
> gl.TexCoord(0., 0.)
> gl.Vertex(-0.5, -0.5, 0.)
>
> --bottom right
> gl.TexCoord(1., 0.)
> gl.Vertex(0.5, -0.5, 0.)
>
> --top right
> gl.TexCoord(1., 1.)
> gl.Vertex(0.5, 0.5, 0.)
> gl.End()
>
> shader:unbind()
>
> end


Multiple bindings of shaders or not available on any hardware. There

can only be one shader at a time running on the GPU. You can however

have multiple compiled shaders that you bind at different times.

On Feb 3, 2008 6:16 PM, Keith Manlove wrote:

> I'm not around my computer to try it, but are multiple bindings

> On Feb 3, 2008, at 1:24 PM, "Wesley Smith" 

> > This is how you use shaders. You just make a shader object and call

> > shader = jit.new("jit.gl.shader", this.drawto)

> > shader.file = "cc.brcosa.jxs" --shader file to load

Multiple bindings of shaders or not available on any hardware.  There
can only be one shader at a time running on the GPU.  You can however
have multiple compiled shaders that you bind at different times.

On Feb 3, 2008 6:16 PM, Keith Manlove  wrote:
> Hey Wesley,
>
> I'm not around my computer to try it, but are multiple bindings
> available?
>
> Keith
>
> On Feb 3, 2008, at 1:24 PM, "Wesley Smith" 
> wrote:
>
>
> > This is how you use shaders.  You just make a shader object and call
> > its bind methods.
> > wes
> >
> >
> > shader = jit.new("jit.gl.shader", this.drawto)
> > shader.file = "cc.brcosa.jxs" --shader file to load
> >
> > function draw()
> >
> >
> > shader:bind()
> >
> > gl.Begin("QUADS")
> > --top left
> > gl.TexCoord(0., 1.)
> > gl.Vertex(-0.5, 0.5, 0.)
> >
> > --bottom left
> > gl.TexCoord(0., 0.)
> > gl.Vertex(-0.5, -0.5, 0.)
> >
> > --bottom right
> > gl.TexCoord(1., 0.)
> > gl.Vertex(0.5, -0.5, 0.)
> >
> > --top right
> > gl.TexCoord(1., 1.)
> > gl.Vertex(0.5, 0.5, 0.)
> > gl.End()
> >
> > shader:unbind()
> >
> > end
>
>


I see... I didn't realize that. I thought that it was only one

shader, but I didn't realize that it was a hardware thing. I'll look

into the multiple binds. Thanks for that.

On Feb 3, 2008 9:16 PM, Wesley Smith wrote:

> Multiple bindings of shaders or not available on any hardware. There

> can only be one shader at a time running on the GPU. You can however

> have multiple compiled shaders that you bind at different times.

> On Feb 3, 2008 6:16 PM, Keith Manlove wrote:

> > I'm not around my computer to try it, but are multiple bindings

> > On Feb 3, 2008, at 1:24 PM, "Wesley Smith" 

> > > This is how you use shaders. You just make a shader object and call

> > > shader = jit.new("jit.gl.shader", this.drawto)

> > > shader.file = "cc.brcosa.jxs" --shader file to load

I see... I didn't realize that.  I thought that it was only one
shader, but I didn't realize that it was a hardware thing.  I'll look
into the multiple binds.  Thanks for that.

On Feb 3, 2008 9:16 PM, Wesley Smith  wrote:
> Multiple bindings of shaders or not available on any hardware.  There
> can only be one shader at a time running on the GPU.  You can however
> have multiple compiled shaders that you bind at different times.
>
> wes
>
>
> On Feb 3, 2008 6:16 PM, Keith Manlove  wrote:
> > Hey Wesley,
> >
> > I'm not around my computer to try it, but are multiple bindings
> > available?
> >
> > Keith
> >
> > On Feb 3, 2008, at 1:24 PM, "Wesley Smith" 
> > wrote:
> >
> >
> > > This is how you use shaders.  You just make a shader object and call
> > > its bind methods.
> > > wes
> > >
> > >
> > > shader = jit.new("jit.gl.shader", this.drawto)
> > > shader.file = "cc.brcosa.jxs" --shader file to load
> > >
> > > function draw()
> > >
> > >
> > > shader:bind()
> > >
> > > gl.Begin("QUADS")
> > > --top left
> > > gl.TexCoord(0., 1.)
> > > gl.Vertex(-0.5, 0.5, 0.)
> > >
> > > --bottom left
> > > gl.TexCoord(0., 0.)
> > > gl.Vertex(-0.5, -0.5, 0.)
> > >
> > > --bottom right
> > > gl.TexCoord(1., 0.)
> > > gl.Vertex(0.5, -0.5, 0.)
> > >
> > > --top right
> > > gl.TexCoord(1., 1.)
> > > gl.Vertex(0.5, 0.5, 0.)
> > > gl.End()
> > >
> > > shader:unbind()
> > >
> > > end
> >
> >
>


I didn't quite follow your last response. What are you trying to do?

Why do you keep talking about multiple binds? A Shader in OpenGL

configures the hardware pipeline to process vertices and pixels in a

particular manner. Obviously, if you only have 1 card, you only have

1 pipeline thus you can only have 1 shader active at any given time.

On Feb 3, 2008 7:31 PM, keith manlove wrote:

> I see... I didn't realize that. I thought that it was only one

> shader, but I didn't realize that it was a hardware thing. I'll look

> into the multiple binds. Thanks for that.

> On Feb 3, 2008 9:16 PM, Wesley Smith wrote:

> > Multiple bindings of shaders or not available on any hardware. There

> > can only be one shader at a time running on the GPU. You can however

> > have multiple compiled shaders that you bind at different times.

> > On Feb 3, 2008 6:16 PM, Keith Manlove wrote:

> > > I'm not around my computer to try it, but are multiple bindings

> > > On Feb 3, 2008, at 1:24 PM, "Wesley Smith" 

> > > > This is how you use shaders. You just make a shader object and call

> > > > shader = jit.new("jit.gl.shader", this.drawto)

> > > > shader.file = "cc.brcosa.jxs" --shader file to load

Hi Keith,
I didn't quite follow your last response.  What are you trying to do?
Why do you keep talking about multiple binds?  A Shader in OpenGL
configures the hardware pipeline to process vertices and pixels in a
particular manner.  Obviously, if you only have 1 card, you only have
1 pipeline thus you can only have 1 shader active at any given time.
Make sense?

On Feb 3, 2008 7:31 PM, keith manlove  wrote:
> I see... I didn't realize that.  I thought that it was only one
> shader, but I didn't realize that it was a hardware thing.  I'll look
> into the multiple binds.  Thanks for that.
>
> Keith
>
>
> On Feb 3, 2008 9:16 PM, Wesley Smith  wrote:
> > Multiple bindings of shaders or not available on any hardware.  There
> > can only be one shader at a time running on the GPU.  You can however
> > have multiple compiled shaders that you bind at different times.
> >
> > wes
> >
> >
> > On Feb 3, 2008 6:16 PM, Keith Manlove  wrote:
> > > Hey Wesley,
> > >
> > > I'm not around my computer to try it, but are multiple bindings
> > > available?
> > >
> > > Keith
> > >
> > > On Feb 3, 2008, at 1:24 PM, "Wesley Smith" 
> > > wrote:
> > >
> > >
> > > > This is how you use shaders.  You just make a shader object and call
> > > > its bind methods.
> > > > wes
> > > >
> > > >
> > > > shader = jit.new("jit.gl.shader", this.drawto)
> > > > shader.file = "cc.brcosa.jxs" --shader file to load
> > > >
> > > > function draw()
> > > >
> > > >
> > > > shader:bind()
> > > >
> > > > gl.Begin("QUADS")
> > > > --top left
> > > > gl.TexCoord(0., 1.)
> > > > gl.Vertex(-0.5, 0.5, 0.)
> > > >
> > > > --bottom left
> > > > gl.TexCoord(0., 0.)
> > > > gl.Vertex(-0.5, -0.5, 0.)
> > > >
> > > > --bottom right
> > > > gl.TexCoord(1., 0.)
> > > > gl.Vertex(0.5, -0.5, 0.)
> > > >
> > > > --top right
> > > > gl.TexCoord(1., 1.)
> > > > gl.Vertex(0.5, 0.5, 0.)
> > > > gl.End()
> > > >
> > > > shader:unbind()
> > > >
> > > > end
> > >
> > >
> >
>


Sorry... I'm a spaz. What I meant to say was, "I'll look into the 

'multiple compiled shaders that you bind at different times' thing." 

It does make sense. Sorry for typing without using my brain.

On Feb 3, 2008, at 9:46 PM, Wesley Smith wrote:

> I didn't quite follow your last response. What are you trying to do?

> Why do you keep talking about multiple binds? A Shader in OpenGL

> configures the hardware pipeline to process vertices and pixels in a

> particular manner. Obviously, if you only have 1 card, you only have

> 1 pipeline thus you can only have 1 shader active at any given time.

Sorry... I'm a spaz.  What I meant to say was, "I'll look into the  
'multiple compiled shaders that you bind at different times' thing."   
It does make sense.  Sorry for typing without using my brain.

> Hi Keith,
> I didn't quite follow your last response.  What are you trying to do?
> Why do you keep talking about multiple binds?  A Shader in OpenGL
> configures the hardware pipeline to process vertices and pixels in a
> particular manner.  Obviously, if you only have 1 card, you only have
> 1 pipeline thus you can only have 1 shader active at any given time.
> Make sense?
>
> wes


jxs shaders in jit.gl.lua?