aalex

Drawing multiple gridshapes without the drawraw seems pretty slow, since it resets the openGL stack everytime it draws one. (as in position, color, rotation, etc.) Regarding this, I can say that a program closer to a scene graph (such as Gem, which I am used to) is easier on the CPU/GPU bus since it doesn't reset the OpenGL stack so open, and it is also easier to position and rotate elements relatively to each other.

Anyways : now I want to drawraw some shapes using Lua. Here is a piece of code. There is the "BindTexture" that doesn't work (expects an integer, id of a texture ??) and some other stuff. Anyone has suggestions on how I could improve this and make it work ? With that, I will be able to create a little Lua library for creating gridshapes and such. Thanks a lot for any input.

test.videoplane = jit.new("jit.gl.videoplane", "output")

test.texture_number = 1 -- how can i get the texture number ?

gl.BindTexture("TEXTURE_2D", test.texture_number)

Hi all, 
Drawing multiple gridshapes without the drawraw seems pretty slow, since it resets the openGL stack everytime it draws one. (as in position, color, rotation, etc.) Regarding this, I can say that a program closer to a scene graph (such as Gem, which I am used to) is easier on the CPU/GPU bus since it doesn't reset the OpenGL stack so open, and it is also easier to position and rotate elements relatively to each other. 

Anyways : now I want to drawraw some shapes using Lua. Here is a piece of code. There is the "BindTexture" that doesn't work (expects an integer, id of a texture ??) and some other stuff. Anyone has suggestions on how I could improve this and make it work ? With that, I will be able to create a little Lua library for creating gridshapes and such. Thanks a lot for any input. 

test = {}
test.videoplane = jit.new("jit.gl.videoplane", "output")
test.videoplane.automatic=0
test.texture_number = 1 -- how can i get the texture number ?

function draw()
  gl.Enable("BLEND")
  gl.BlendFunc(6,1)
  gl.Disable("DEPTH_TEST")
  gl.Color(1,1,1,0.3)
  gl.Scale(0.1,0.1,1)
  gl.BindTexture("TEXTURE_2D", test.texture_number)

  for i=1,100 do
  	gl.PushMatrix()
  	  gl.Translate(i/150.0,0,0)
      gl.Rotate(i,0,0,1)
      test.videoplane:drawraw()
    gl.PopMatrix()
  end
end


drawraw-in-jit-gl-lua

use jit.gl.bindtexture(texturename, textureunit)

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

> Drawing multiple gridshapes without the drawraw seems pretty slow, since it resets the openGL stack everytime it draws one. (as in position, color, rotation, etc.) Regarding this, I can say that a program closer to a scene graph (such as Gem, which I am used to) is easier on the CPU/GPU bus since it doesn't reset the OpenGL stack so open, and it is also easier to position and rotate elements relatively to each other.

> Anyways : now I want to drawraw some shapes using Lua. Here is a piece of code. There is the "BindTexture" that doesn't work (expects an integer, id of a texture ??) and some other stuff. Anyone has suggestions on how I could improve this and make it work ? With that, I will be able to create a little Lua library for creating gridshapes and such. Thanks a lot for any input.

> test.videoplane = jit.new("jit.gl.videoplane", "output")

> test.texture_number = 1 -- how can i get the texture number ?

> gl.BindTexture("TEXTURE_2D", test.texture_number)

jit.gl.bindtexture(tex.name, 0)
drawobject()
jit.gl.unbindtexture(tex.name, 0)

On 7/14/07, Alexandre Quessy  wrote:
>
> Hi all,
> Drawing multiple gridshapes without the drawraw seems pretty slow, since it resets the openGL stack everytime it draws one. (as in position, color, rotation, etc.) Regarding this, I can say that a program closer to a scene graph (such as Gem, which I am used to) is easier on the CPU/GPU bus since it doesn't reset the OpenGL stack so open, and it is also easier to position and rotate elements relatively to each other.
>
> Anyways : now I want to drawraw some shapes using Lua. Here is a piece of code. There is the "BindTexture" that doesn't work (expects an integer, id of a texture ??) and some other stuff. Anyone has suggestions on how I could improve this and make it work ? With that, I will be able to create a little Lua library for creating gridshapes and such. Thanks a lot for any input.
>
>
> test = {}
> test.videoplane = jit.new("jit.gl.videoplane", "output")
> test.videoplane.automatic=0
> test.texture_number = 1 -- how can i get the texture number ?
>
> function draw()
>   gl.Enable("BLEND")
>   gl.BlendFunc(6,1)
>   gl.Disable("DEPTH_TEST")
>   gl.Color(1,1,1,0.3)
>   gl.Scale(0.1,0.1,1)
>   gl.BindTexture("TEXTURE_2D", test.texture_number)
>
>   for i=1,100 do
>         gl.PushMatrix()
>           gl.Translate(i/150.0,0,0)
>       gl.Rotate(i,0,0,1)
>       test.videoplane:drawraw()
>     gl.PopMatrix()
>   end
> end
>
>
>


https://cycling74.com/forums/index.php?t=msg&th=24491&start=0&rid=0&S=aa8f6e5cd6a96801a0bbc8a7bbbda727

Two questions : drawobject() is a method of gridshapes, for instance, right ?

Also, how can I retrieve the name of a texture that is into a jit.gl.texture object in a patcher ?

I guess using gl.Start("QUADS") is faster than using gridshapes ?

Hi, 
I also found this : https://cycling74.com/forums/index.php?t=msg&th=24491&start=0&rid=0&S=aa8f6e5cd6a96801a0bbc8a7bbbda727

Also, how can I retrieve the name of a texture that is into a jit.gl.texture object in a patcher ? 

> Two questions : drawobject() is a method of gridshapes, for instance, right ?

All opengl Jitter objects have 2 draw methods. For example:

gs = jit.new("jit.gl.gridshape", this.drawto)

> Also, how can I retrieve the name of a texture that is into a jit.gl.texture object in a patcher ?

You can't! If you already know thhe name, you can use it directly hoewever.

> I guess using gl.Start("QUADS") is faster than using gridshapes ?

This depends. gridshape is limited to certain forms. It also has

displaylists which are fast as long as your geometry is static.

jit.gl.mesh will be fast for dynamic data but requires vertices to be

stuffed into a matrix. Using gl.Begin("QUADS") is nice for generative

algorithms and things that don't fit easily into a matrix. Each has

On 7/18/07, Alexandre Quessy  wrote:
>
> Hi,
> I also found this : https://cycling74.com/forums/index.php?t=msg&th=24491&start=0&rid=0&S=aa8f6e5cd6a96801a0bbc8a7bbbda727
>
> Two questions : drawobject() is a method of gridshapes, for instance, right ?

gs = jit.new("jit.gl.gridshape", this.drawto)
gs:draw()     --draws and sets state
gs:drawraw() -- draws only

> Also, how can I retrieve the name of a texture that is into a jit.gl.texture object in a patcher ?
>

You can't!  If you already know thhe name, you can use it directly hoewever.

> I guess using gl.Start("QUADS") is faster than using gridshapes ?
>

This depends.  gridshape is limited to certain forms.  It also has
displaylists which are fast as long as your geometry is static.
jit.gl.mesh will be fast for dynamic data but requires vertices to be
stuffed into a matrix.  Using gl.Begin("QUADS") is nice for generative
algorithms and things that don't fit easily into a matrix.  Each has
its own purpose.

It seems like my textures are not found when I use thisl :

jit.gl.bindtexture(my.dots[x][y].frame .. my.tex.SUFFIX, 0)

(the concatenation above generates the name of an existing texture) I think there should be a way to specify a named render context into which the textures are stored.

Namely, there are somewhere in my open patches objects like this : [jit.gl.texture output 1-xxx], so I should specify in some way the "output" render context.

For optimization, I think that the fastest and easiest way to do little 2D games in Lua/Jitter might be using the method above. [jit.gl.mesh] are nice, but not as flexible, at least when you are not much used to it.

Hi, 
It seems like my textures are not found when I use thisl : 

jit.gl.bindtexture(my.dots[x][y].frame .. my.tex.SUFFIX, 0)
(and then the gl.Begin("QUADS") stuff)

(the concatenation above generates the name of an existing texture) I think there should be a way to specify a named render context into which the textures are stored. 

> It seems like my textures are not found when I use thisl :

> jit.gl.bindtexture(my.dots[x][y].frame .. my.tex.SUFFIX, 0)

Well, if indeed the name is correct and your jit.gl.lua object's

drawto attribute is the same as the texture's, then there should be no

issues. It works. This I know. From what you've posted I can't

really say more than that. jit.gl.bindtexture get's the context name

from the drawto attribute of the object the script is embedded in.

On 7/18/07, Alexandre Quessy  wrote:
>
> Hi,
> It seems like my textures are not found when I use thisl :
>
> jit.gl.bindtexture(my.dots[x][y].frame .. my.tex.SUFFIX, 0)
> (and then the gl.Begin("QUADS") stuff)
>

Well, if indeed the name is correct and your jit.gl.lua object's
drawto attribute is the same as the texture's, then there should be no
issues.  It works.  This I know.  From what you've posted I can't
really say more than that.  jit.gl.bindtexture get's the context name
from the drawto attribute of the object the script is embedded in.

In all the tests I have done, a [jit.gl.texture] that is created in a patcher could not be accessed and drawn on a "gl.Begin()..." from a Lua script.

Hi, 
In all the tests I have done, a [jit.gl.texture] that is created in a patcher could not be accessed and drawn on a "gl.Begin()..." from a Lua script. 

function draw()
	jit.gl.bindtexture("ptex", 0)
	gl.Color(1, 1, 1, 1)
	gl.Begin("QUADS")
		gl.TexCoord(0, 1)
		gl.Vertex(-1, 1, 0)

		gl.TexCoord(1, 0)
		gl.Vertex(1, -1, 0)

		gl.TexCoord(0, 0)
		gl.Vertex(-1, -1, 0)
	gl.End()
	jit.gl.unbindtexture("ptex", 0)
end


drawraw in jit.gl.lua