Switching from image to textures.

[OutlawLee]

I want to load a  texture onto a texture. (before i loaded a image and a image with copy)

or should i can i make image onto a texture ? which is better ?
btw this is my TextureManager.cpp (changed from ImageManager.cpp)


I used to have:

sf::Image tileset;
sf::Image tileImage;
tileImage.Copy(tileset, 0, 0, sf::IntRect(x * tileSize, y * tileSize, frames * tileSize, tileSize), true);

But now i switched my code all to sfml 2.0 and i dont know the function that copies in sfml 2.0.

i want something like this:

sf::Image tileset;
sf::Texture tileTexture;
tileTexture.Copy(tileset, 0, 0, sf::IntRect(x * tileSize, y * tileSize, frames * tileSize, tileSize), true);

edit:

I searched a bit, and i think i could use loadFromImage but im not sure how. An example with the code above would be appriciated.

edit2:

Maybe this ? but im lacking the 0,0 position, maybe texture.update ?

tileTexture.loadFromImage(tileset, sf::IntRect(x * tileSize, y * tileSize, frames * tileSize, tileSize));
 

edit3:

I managed to fix the errors. Can someone tell if this code does like the past one ?

sf::Image tileset;

sf::Texture tileTexture;
tileTexture.create(tileSize, tileSize);
tileTexture.loadFromImage(tileset, sf::IntRect(x * tileSize, y * tileSize, frames * tileSize, tileSize));
tileTexture.update(tileset, 0, 0);
 

I have the correct tileSize declaration. i dont get any errors when compile.

ty

[Laurent]

You can either:

• do all your image manipulation as before with sf::Image, and then call texture.loadFromImage(image)
• you can create an empty texture (texture.create) and copy images to it with texture.update

[OutlawLee]

I think i did what you said in your second option right ?

Create a new texture and load the image inside it.

[Laurent]

But are you copying tiles from a big tileset into individual small textures?

[OutlawLee]

Everything works properly if i comment:

tileTexture.update(tileset, 0, 0);

right now the code is:

sf::Texture tileTexture;
tileTexture.create(tileSize, tileSize);
tileTexture.loadFromImage(tileset, sf::IntRect(x * tileSize, y * tileSize, frames * tileSize, tileSize));
 

[Laurent]

You didn't answer to my question, and the call to create is useless.

[OutlawLee]

Ups, i edited the message and removed it.

Yes, im loading a big one and then cliping it.

[Laurent]

Yes, im loading a big one and then cliping it.

Why? This is the worst strategy if you want to get good performances. Switching textures is an expensive operation for the graphics card, having everything in the same texture is more optimized. That's the reason why the sf::Sprite class has a TextureRect property.

[OutlawLee]

Oh loading once big pic into a texture and then splitting it into sprites is pretty logical.

argh, im such a noob need to learn classes and arrays to make it properly-

Laurent, is this
http://en.sfml-dev.org/forums/index.php?topic=3023.0
system good ? I will jsut edit it for sfml 2,0

[Laurent]

Laurent, is this
http://en.sfml-dev.org/forums/index.php?topic=3023.0
system good ?

I have no idea.

But probably not: SFML 2 provides an optimized way of creating large batches of static geometry (with vertex arrays); tilemaps are a typical use case for this.