Better FPS drawing 10.000 sprite

[Ptlomej]

i draw about 100*random(100,500) Sprites with a little trick and high performance

[TheEnigmist]

i draw about 100*random(100,500) Sprites with a little trick and high performance

Can you explain how or it's a secret?

[Ptlomej]

Here and example

i have an Area 1000x1000.
I create now 100 sf::Images

Code: [Select]


for(int x = 0; x != 100; x++){
    sf::Image *Chunk = new sf::Image;
    Chunk->Create(1000,1000);
}


Then i add all the Objects that are on this area schould be with

Code: [Select]


Chunk->Copy(Exampleimage,X,Y,IntRect(0,0,Exampleimage.GetWidth(),Exampleimage.GetHeight()),true);


then convert to the sprites and add too sprite list

Code: [Select]

Texture *tChunk = new Texture;
tChunk->LoadFromImage(Chunk,IntRect(0,0,1000,1000));
Sprite *sChunk = new sf::Sprite(*tChunk);
sChunk->SetOrigin(0,0);
sChunk->SetPosition(sf::Vector2f((float)xCount,(float)yCount));
BackgroundChunks.push_back(sChunk);

generate new position for the next "chunk"

Code: [Select]

xCount += 1000;
xCounter++;
if(xCount == 5000){
xCount = -5000;
yCount += 1000;
xCounter = 0;
yCounter++;
}

and then Draw the 100 Sprites

Code: [Select]

for(list<sf::Sprite*>::iterator IT = BackgroundChunks.begin(); IT != BackgroundChunks.end(); IT++){
_RenderWindow->Draw(**IT);
}

its very simple

[Nexus]

Ptolemaj, why are you using pointers and new? There's no reason, just use std::vector<sf::Sprite> or std::vector<sf::Texture>. It's even faster, since not every sprite/texture is allocated on its own. Same applies for the usage of vector instead of list. And avoiding manual memory management is simpler and less error-prone.

And why don't you directly have a sf::Texture with the needed sub-rects?

[Mjonir]

Just a word on SFML performance in drawing a lot of sprites:

I have a benchmark for my engines that creates 500 animated objects, each with an independent and quite complex (voluntarily unoptimized! It could easily be!) move sequence that is computed in Lua. I get about 35 FPS.  A simpler move sequence gives me around 110 FPS.

I was curious so I programmed a little profiling lib today and checked where the horsepower was going:

- 95% of the time is spent calculating the next frame.
- Which means only 5% of the frame is spent drawing.
- Out of the 95%, about 1 or 2% is checking keyboard/mouse/window events
- I'd say 2% for the engine itself (collision detection, etc.)
- 90% spent computing the move sequences (it's sequential, unoptimized, very complex and goes through a Lua interpreter, but still that's the kind of complexity you could easily get for a "whole city" above .

Even better, I have an option on my engine that separates the update from display, and thus on a dual core display doesn't even matter at all.

That's to say: Don't worry too much about drawing lots of sprites, that's maybe not your bottleneck thanks to SFML.

[mateandmetal]

Code: [Select]


for(int x = 0; x != 100; x++){
    sf::Image *Chunk = new sf::Image;
    Chunk->Create(1000,1000);
}


I see memory leaks  :lol:

Btw..What about using tilemaps for the city? Drawing a tilemap using VertexArray is very fast

[Nexus]

I agree with Mjonir. You also have to make sure you are compiling with the right features, e.g. release mode. Also start without debugger (even in release mode), it can make a huge difference, especially for dynamic allocations. Also, some STL implementations use error checks that need to be disabled manually.

[TheEnigmist]

I agree with Mjonir. You also have to make sure you are compiling with the right features, e.g. release mode. Also start without debugger (even in release mode), it can make a huge difference, especially for dynamic allocations. Also, some STL implementations use error checks that need to be disabled manually.

Is it a good idea to disable STL error checks? Do they take much memory to check errors?

[drifton]

two things that will greatly improve tiles on today's hardware,  vba/vbo and texture atlas/ ie compiling all your sprites and tiles into one texture/image,

steps process map to determine number of quads needed for background, fringes , transitions, buildings, ect...

apply uv that reference the tile image in the atlas/tilesheet what ever you really want to call it

draw base tile/fringe vbos
draw objects (characters, chests, npc's , enemies)  vbo
draw cover tile vbo
done

even with alpha blendening you are looking at very few triangles being drawn for today'a hardware
point in case 1920x1080 screen filled with 16x16 tiles with 4 layers = 32,400 tiles per frame or ~ 3.89 million triangles per-second and even the old geforce 2 could draw ~25 million triangles per second



and that really is all brute force with out you dropping the tiles in the 3 top layers that are not drawn out of the vertex buffer and in most cases are just empty space in my game and i actually have several smaller buffer so that it's easier on me to just update tiles like water animation every few frames / characters