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

RenderReadPixels / UpdateTexture upside-down #1653

SDLBugzilla opened this issue Feb 10, 2021 · 0 comments

RenderReadPixels / UpdateTexture upside-down #1653

SDLBugzilla opened this issue Feb 10, 2021 · 0 comments


Copy link

@SDLBugzilla SDLBugzilla commented Feb 10, 2021

This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

Reported in version: 2.0.3
Reported for operating system, platform: Linux, x86_64

Comments on the original bug report:

On 2014-09-24 17:04:54 +0000, sanette wrote:

If I RenderReadPixels
and then immediately use the pixel data in UpdateTexture,
then the image is upside-down

On 2014-09-24 17:05:25 +0000, sanette wrote:

I'm using the opengl renderer

On 2014-09-25 06:53:42 +0000, sanette wrote:

Created attachment 1881
pixels upside-down

On 2014-09-25 06:54:24 +0000, sanette wrote:

of course, if I remove the specific code to put pixels top-down
in src/render/opengl/SDL_render_gl.c (see patch) then this works...
but this is very strange.

On 2014-09-26 14:16:46 +0000, sanette wrote:

the upside-down behaviour was noticed already in Bug 2705

On 2015-02-19 06:32:16 +0000, Ryan C. Gordon wrote:

Marking a large number of bugs with the "triage-2.0.4" keyword at once. Sorry
if you got a lot of email from this. This is to help me sort through some bugs
in regards to a 2.0.4 release. We may or may not fix this bug for 2.0.4,

On 2017-08-14 05:01:27 +0000, Sam Lantinga wrote:

Ryan, can you make sure we're reading the pixels the right way for 2.0.6?

On 2017-10-21 12:58:40 +0000, Sylvain wrote:

I tried various configuration (with and without RenderTarget, renderer opengl) and I believe this is fixed.

Very likely with:

On 2017-10-21 17:11:17 +0000, Sam Lantinga wrote:

Okay, can you please reopen this if you're still seeing the problem?


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

1 participant