Elysian Shadows

Hello everybody,

First question is: What is the difference between Texture and Surface in SDL v2 ?
Second question: Why the texture rendering is stretched ?

bool CTexture::OnDraw(SDL_Renderer* Renderer, SDL_Texture* Texture, int XDest, int YDest)
{
    if(Renderer == NULL || Texture == NULL)
    {
        cerr << "Can't render texture [SDL_Error: " << SDL_GetError() << "]" << endl;
        return false;
    }

    SDL_Rect DRect;

    DRect.x = XDest;
    DRect.y = YDest;
    
    // This function stretchs the texture ????!!!
    SDL_RenderCopy(Renderer, Texture, NULL, &DRect);

    return true;
}

PS: Please, explain me when do we use Surface and when do we use Texture in SDL v2.

Thank you in advance.

Well, afaik.. Surfaces are stored in client-side memory, so they're actually just abstractions in that sense, whilst the textures are tied to a context which is the renderer and that means it's likely stored on the GPU or as close to video memory as possible (which means they can be hw accelerated). If that's the case, slow or otherwise heavy computations done can benefit greatly from this.

SDL_RenderCopy clips the destination rect against the viewport and then compensates for, or rather adjusts the source appropriately if I'm not mistaken. You would probably benefit from using SDL_RenderCopyEx instead.

EDIT: Missed the second question.

Please, can you explain it to me.
When do we use Surface ? And, when do we use Texture in SDL v2 ?

heisenberg wrote:Please, can you explain it to me.
When do we use Surface ? And, when do we use Texture in SDL v2 ?

I thought my initial response explained that sufficiently.

You only want to really use surfaces when there's *need* for processing pixels on the CPU, because why be doing things slower when there're clear ways of doing it more efficiently without added layers of complexity on there.

As D-e-X said, use Texture whenever possible to keep the data in VRAM. If you need to do software rendering or processing (sllooww), then use the Surface representation in RAM.

Thank you guys for your answers.