Organized Structure of Rendering in Different Game "States" (LWJGL)

[sproingie]

Like whats a power of 2 texture, and why cant I just load any image.
Whats a spriteBatch or textureAtlas; why are these things needed or at least so very encouraged.

Slick2D won't really let you get away without knowing these things either.  Try tiling your NPOT texture in slick, or managing a couple hundred individual texture objects without using a SpriteSheet.

[Cero]

Like whats a power of 2 texture, and why cant I just load any image.
Whats a spriteBatch or textureAtlas; why are these things needed or at least so very encouraged.

Slick2D won't really let you get away without knowing these things either.  Try tiling your NPOT texture in slick, or managing a couple hundred individual texture objects without using a SpriteSheet.

if by tilting you mean rotation: works just fine.
we actually only use tilesheets, everything else is still individual images. Works just fine. Of course it depends on how you do it.
If your textures are like 200x300, and you will only use 512x512 textures MAX, using spritesheets is not really useful, if you can hardly put 2 sprites on there.

Example : http://southtownexpress.deviantart.com/art/Takuma-KoF-XIII-Sprite-Sheet-279236989

I wouldn't want to make on image with an height of 17000 pixel =D
We do 512 or 1024 max, for compatibility reasons.

[sproingie]

I said tiling, as in "to tile".  IIRC, slick will pad it out to POT dimensions, which makes it not a tileable texture.

One texture per sprite is reasonably common for characters with very smooth animations.  I'm talking about one texture per frame, and yes some people actually try to do that.

Games published by our own members! Check 'em out!

[Cero]

I said tiling, as in "to tile".  IIRC, slick will pad it out to POT dimensions, which makes it not a tileable texture.

One texture per sprite is reasonably common for characters with very smooth animations.  I'm talking about one texture per frame, and yes some people actually try to do that.

ah yes, I read tilTing, as in rotation I guess
(Slick hacks it so that an Image has the correct width and height, not POT, so tiling that way does actually work)

yeah for tiles you really have to use a proper implementation, in my case tilesheets and vbo's

well yeah, eventually we are going to do it properly too, we just want to release something first
anyway my point is, that it's nice slick at least lets you do this

[davedes]

IIRC tiling works fine for NPOT textures since Slick doesn't rely on GL_REPEAT. The texture fills just draw multiple quads within the same glBegin/glEnd. The downside of course is that seams will show if the texture uses GL_LINEAR and is being scaled.

For tiles VBOs won't help too much -- most of the performance loss comes from fill rate (or state switching if you aren't mindful).

[JESTERRRRRR]

I also like and reccomend Java2D to begginers, I would of made no progress if i hadn't been able to draw game graphics with the ease of Java2D. Now onto opengl tho ^^