Why is my WebGL texture upside-down?
To get a texture into your WebGL program,
and since you’re on the web, you’ll probably use an
<img> element or similar as the source for the texture.
If you do, you’ll be in for a confusing surprise when you render the texture:
The Y-axis is flipped!
Here’s why, and how to fix it.
But if you’re just here for the solution, you want:
texImage2D function is a thin wrapper over
glTexImage2D C function.
This C function does not take an
it just takes a
const void * data.
It expects the pixels in that array to be stored in bottom-to-top order:
The first element corresponds to the lower left corner of the texture image. Subsequent elements progress left-to-right through the remaining texels in the lowest row of the texture image, and then in successively higher rows of the texture image. The final element corresponds to the upper right corner of the texture image.
the spec for the WebGL
The first pixel transferred from the source to the WebGL implementation corresponds to the upper left corner of the source.
So, the browser copies pixels from the
<img> in top-to-bottom order,
even though OpenGL expects them in bottom-to-top order!
I can think of no reason for this perverse behavior
except that it’s a mistake in the design of WebGL.
Happily, the spec basically admits that it’s a mistake, and provides a way to fix this behavior:
This behavior is modified by the
UNPACK_FLIP_Y_WEBGLpixel storage parameter, except for
ImageBitmaparguments, as described in the abovementioned section.
So, it’s highly likely that you want this for every program you write:
const gl = displayCanvasEl.getContext("webgl"); gl.pixelStorei(gl.UNPACK_FLIP_Y_WEBGL, true);
Strangely, you won’t find this advice on MDN or elsewhere.
More by Jim
- Your syntax highlighter is wrong
- Granddad died today
- The Three Ts of Time, Thought and Typing: measuring cost on the web
- I hate telephones
- The sorry state of OpenSSL usability
- The dots do matter: how to scam a Gmail user
- My parents are Flat-Earthers
- How Hacker News stays interesting
- Project C-43: the lost origins of asymmetric crypto
- The hacker hype cycle
- The inception bar: a new phishing method
- Time is running out to catch COVID-19
- A probabilistic pub quiz for nerds
- Smear phishing: a new Android vulnerability