I want to get additional api for spitebatches, like attached attributes for fragment shaders or setting different shaders for groups of sprites into one spritebatch, but it's hard, i think. You can access sprite vertex attributes in a vertex shader for future calculations and then use varying varia...

[wiki]SpriteBatch:attachAttribute[/wiki] lets you attach a vertex attribute from any mesh to any SpriteBatch. You can even override existing attributes used by the SpriteBatch like colors (the "VertexColor" attribute), so you can implement custom per-vertex colors, texture coordinates, po...

Well, you will have a bottleneck if your sprites are going to be updated every frame, but in my application where i have, say, 20k of static sprites and around 500 dynamic, constantly updated sprites in a separate spritebatch, i don't really see much of a drop below 60 fps. But i imagine someone hav...

Unless I got what you meant completely wrong :? The idea was to make a module that receives pattern parameters (by passing them as a table to it, by calling setter functions, by specifying preset file etc) and the canvas (or maybe raw imagedata object? canvas is way faster to draw on tho) where use...

Any chance you will release separate generator class for others to use in their projects? Like, for example, if i created nice pattern which i like, then save some sort of parameters into a file, and then by including this generator class into my project and feeding previously created file to this c...

Looks solid. Reminds me of an old game Spheres of Chaos (video is about 2012 remake, i think).

But one should also try and reuse the userdata types, more than the objects themselves. It is trivial for a particle emitter, since you can set any value to previously created one before with no problem, but i'm not sure about physics. Few examples - i found no way to change shape's dimensions or l...

I wouldn't do this until you start having problems with GC pauses though, because it costs CPU to keep marking objects each frame. And that is another reason why i don't want to rely completely on GC, since in my application, there can be a situation with object creation spike, and while instantiat...

Glad i've got pretty insightful opinion on the subject. I have the exact opposite opinion. :) The garbage-collector exists with the sole aim to relieve us, the programmers, of additional concerns about memory shenanigans. Why should I spend time and code in relieving it from what it does best? ;) I ...

I'm generally really concerned on resource usage and in not wasting CPU/memory, but is it really worth in this case? Well, ofcourse, not always. Any wild and premature optimization usually ends up doing directly opposite to what it was initially designed for. So it depends on system architecture, a...