I tried to use uthash in cocos2d, but uthash has an strange bug.
When you include uthash.h in your project (you don’t need to use it), your game will perform ~5% worse.
I don’t think it’s a uthash bug. Instead I think it’s a gcc, but anyway, it’s a nasty bug.
Now, in cocos2d, I’m using a modified version of Chipmunk’s cpHashSet.

I am experimenting with this myself at the moment. One way to do this is to load an images vertices, tex coords and colour info into an Interleaved vertex array. Then when updating the location of the image, you just change the vertices for that image in the IVA, you don’t change the tex coords. I’m doing this in a skunk works I’ve got going by registering every new Image with my Render Manager which returns to the Image class a pointer to an entry in the IVA. This entry contains a structure which holds the vertices, tex coords and colour info.

In the Image then I can make changes directly to the data in the IVA, say vertices only and leave the tex coords and colour info untouched.

It also means I keep a copy of the original vertices, tex coords and colour info within the image as well, so I can transform the original i.e. translate or rotate and put the results straight into the pointer into the IVA. At the moment this is given me around 500 quads with blending on the screen at 30fps, which I don’t think is that bad.

Mike

I’m sure there must be a way of doing this with interleaved data, but I can’t see anything obvious with my very limited experience of this stuff.

For some things though, games being one of them, there are good reasons for using structures and its something I’ll go back and change.

I’m planning once I’ve got all of the core topics covered to go back and work on enhancing the code to improve performance. I’ve already created a new render manager which batches up geometry, texture and colours into a single Interleaved Vertex Array and loads that into a Vertex Buffer Object from where it renders. I’m not going to be releasing that code just yet as I’ve got more work I want to do on it, but it will find its way into a tutorial at some point :o)

In the mean time, if anyone has made changes to the code from the blog which has improved performance and wants to share, please feel free :o). Some have already been sharing their findings and its great to see what ingenious ideas people have around common problems.

Mike

What I’ve done is to create an array of all possible tiles in the MapSet class. This may use very slightly more memory for each tile, however, this way all the vertices and texture coords can just be referenced in glDrawElements. I then have a renderTileID:theID x:coordX y:coordY which handles all the buffering as 1 tileset normally equates to 1 texture.

Hope this helps it’s working nicely for me although I still need to optimise further to get up to 60fps with touches.

@IPhoner
In a font, there are certain pairs of letters that have different spacing between them. for example in “Wo” there’s less space between the W and the o than in “WO”. This pairs of letters are called kerning pairs, and the space between them is called kerning.

PS. I still plan to release my own classes sometime in the future but I need to get some free time to add some features which I personally don’t use but that any self-respecting font class should have :P