Texture.readPixels() only returns top slice of 3D textures

Bugs
,
1

I noticed that when I call readPixels() on a 3D texture, it only returns a buffer containing top 2D slice of pixel data. In the linked example, I create a 2x2x2 3D texture a fill it iteratively with data. I then log the data array and see the expected 2 x 2 x 2 x 4 = 32 data points. After the data is fed to a RawTexture3D, I read the textures pixels but only see the first 16 data points.

I’m not sure if this should be considered a bug or a feature request. On one hand, it seems like the readPixels() method oriented toward 2D textures because there is no depth parameter. However, it also seems like the method isn’t doing what it should when readPixels() doesn’t read all the pixels by default.

2

Indeed, readPixels is meant to read 2D textures at the time, and because there’s no layerIndex parameter, it gets the first layer in the case of a 2DArrayTexture / 3DTexture.

You can create an issue in our repo about this and we will see what we can do about it.

1 Like
3

Thanks for the clarification. Should I create the issue as a bug or a feature?

4

It would be an enhancement, so “new feature” in the template.

1 Like