Question for best performance

[roccio]

Hello, I have a big texture (up tp 4096 or 8192) that is the background of my game. I would like to know what is better to render, one big rect with the same size of the texture, or a rect large as the game window and scrolling the textureRect, or split it in several tiles everyone mapped with the corrects coordinates inside the big texture.

Thank you for your advise!

[Laurent]

It depends on which hardware you plan to make your app work. If you target low-end machines, then you'll have to split your images to 512x512 (that's the maximum reliable texture size) anyway.

[Nexus]

You could also have a look at thor::BigSprite and thor::BigTexture. They can split images automatically for you.

However, it may be easier (and potentially more efficient) to use smaller textures in the first place, if you know you want maximum portability.

[roccio]

Ok, I will go in the split way. Thank you very much!

[Jabberwocky]

It depends on which hardware you plan to make your app work. If you target low-end machines, then you'll have to split your images to 512x512 (that's the maximum reliable texture size) anyway.

That's really low end hardware.
Like maybe a cheap tablet?  Or 15 year old computer?

But yeah, an 8192x8192 texture is going to chew up a gfx card's memory pretty fast.

8192x8192x4 = 256 MB vram in one texture.
Don't do that - split it up as others have recommended.

[Laurent]

That's really low end hardware.
Like maybe a cheap tablet?  Or 15 year old computer?

I'd say Intel integrated chips from only a few years back, like many laptops have. But yeah, maybe now 1024x1024 can be considered safe too.

[Jabberwocky]

I'm pretty sure you'd have to go back at least a decade to find an intel integrated card incapable of handling 1024x1024.

[roccio]

Thanks all.
But the real question is:

is better to have few big sprites or many little ones?

[Laurent]

is better to have few big sprites or many little ones?

Obviously few big ones : that's less points to transform and less driver calls, for the same amount of pixels drawn.