I am no pro when it comes to LUA but in your case bullets is a structure/array of numbers specific for a bullet object not an array of objects.

To have some class-like functionality read : http://lua-users.org/wiki/SimpleLuaClasses

You are heavily overthinking something here. It's the most simple way I can think of. Make the routine customizable so it would depend on the number of rows. Divide each menu box into 3 parts : top, middle and bottom. Each time draw the top and the bottom and draw the middle row as many times as nee...

All I'm seeing her is that the menu is separated into several rows and each row is drawn separately with a ~150ms delay.

I'm sorry but I don't really get what you are trying to achieve. And the fact that there is no bullets array in your code isn't helping either

@Ref

In case you've wondered your attachment works fine on my radeon. It created artifacts on my PC at work.

To anyone wondering what was the problem.


I had to resize the extern vec2 mass[512] to 255 elements. Don't ask me why more caused the flickering. So far only the ATI had the problems

As my issue was lost in the previous post I am having high hopes the problem might get noticed now. [Probable ATI Driver Bug = Love's code isn't 100% safe] My draw function consists of a loop and with each cycle I send an array of data to the shader. The problem is a black blinking square on the scr...

Not really I believe this is the kind of situation when you either know what's wrong or not. But maybe it's just me :). MassMtx is a [j][2] Matrix that works correctly. Vsync is on . Very well then. This is the shader code : extern number mapx; extern number map_xoffset; extern number blocksize; ext...

Ok double posting and bumping :awesome: I have managed to get some effects out of the cumbersome Love2d ;) (no srsly, the bugs are killing me when I want to do something more advanced). I diagnosed an issue that I find hard to solve. My draw function consists of a loop and with each cycle I send an...

I just want to make sure that once my shader code gets big I won't have to spend a couple of hours figuring what's wrong while one of my variables has been thrown away just because. I need to make sure all the things I introduce stay there.