devkitPro

Update 04/02/2011

• Added gl[Get/Set]ActiveTexture() for Stencil FX (See Sprites example)
  Added uoff and voff to glSpriteOnQuad for more FX
  Changed Sprite Examples

glLoadTileset() can load single tiles. Just use the same tilesize and bmpsize in your parameters and it would load a single tile.

You can use the returned textureID to delete your textures at runtime. ie. Dynamic textures.

work through the nehe examples first. hm okay I will do this. How is it possible to animate the models? I mean when I load a mesh it is static and not formable. Do I have to code the polygons and vertexes and change the positions of them to animate something, isn't there no better way? That's about...

Very interesting discussion: I´m getting lost Just a small question to the authors: To put sprites at different depths I asume you just has to say glTraslate(0,0, whateverZyouwant); glSprite(...) Am I right??? No. Depth management is handled automatically by the library. Just call glSprite() and yo...

if GL2D gets integrated, I'll prolly just keep glSprite() for speed, and do a glSpriteRotateScale() that can be a generic function for all sprite needs so as not to pollute the global namespace.

What do you guys think?

Enay: LibNDS 1.5.0 can do dynamic textures. Just glDeleteTexture() when you want to unload it. Then do a glLoad[Sprite/Tile]set() after that to load another texture. Should work as long as you have enough VRAM allocated for textures. BTW, pls. vote on the poll WM added. edit: Could we have a look-se...

Aaaah, no. That might explain everything ;) [edit]Updated! Looks like the GL2D library has changed a bit to do with pallettes so I need to modify my source code. By the way Relminator I've also just reminded myself of something, in the features list you mention that this library supports 'alpha' bu...

Yo, Enay. I have just updated the lib. See if it fixes some of the issues you posted.

Better Docs too.

;*)

For primitives, there's really no way to have a memleak as they don't allocate stuff. I fact even the glSprite routines never allocate anything so memleak should not be an issue.

I'll look into it. I may have uploaded an older build.

Yep:
Just ad that code and your done.


Enay, thanks for the heads up. I'll fix it.