Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDL_LockTexture has inconsistent behaviour with different render drivers #654

Closed
SDLBugzilla opened this issue Feb 10, 2021 · 0 comments
Closed
Labels
wontfix This will not be worked on

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

Reported in version: HG 2.0
Reported for operating system, platform: All, All

Comments on the original bug report:

On 2012-08-27 04:38:05 +0000, Pallav Nawani wrote:

Under OpenGL, SDL_LockTexture () provides access to potentially random data from system RAM. Under Direct3D, SDL_LockTexture() does actually provide access to Texture Data.

In particular this sequence will completely clobber the texture data under OpenGL:

SDL_LockTexture();
SDL_UnlockTexture();

While it will work fine under Direct3D.

This bug just caused me 3 wasted days >/

On 2012-09-28 03:30:40 +0000, Sam Lantinga wrote:

This is an intentional optimization to make streaming textures as fast as possible.
The documentation on the wiki has been clarified:
http://wiki.libsdl.org/moin.cgi/SDL_LockTexture

Thanks!

@SDLBugzilla SDLBugzilla added bug wontfix This will not be worked on labels Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant