(docs) Missing changelog/docs for r126 WebGLRenderTarget.setTexture

[nyan-left]

r126 introduced setTexture within WebGLRenderTarget. This is not documented in the release. Looks like there's no mention of it in the docs either.

The release notes + docs should be updated to reflect this addition.

Relevant commit here.

Happy to help out with the docs if needed. Thanks!

[Mugen87]

This method is only used at one place in the entire code base:

three.js/examples/webgl2_rendertarget_texture2darray.html

Line 147 in 507459c

renderTarget.setTexture( renderTargetTexture );

Um, I wonder if we could remove the method and solve the use case in the example differently. Maybe just inlining the code of setTexture() in the example?

[Mugen87]

I wonder if it isn't better to introduce something like WebGL3DRenderTarget and/or WebGL2DArrayRenderTarget.

The current way of assigning a custom texture to WebGLRenderTarget feels like a hack to me. The texture reference of a render target should not be replaced.

[gkjohnson]

I've used the setTexture function to render to a texture 2d array but it felt like a bit of a hack to me, too, if only because it's undocumented. Adding WebGL3DRenderTarget and WebGL2DArrayRenderTarget seem like good solutions that line up with the other three.js classes. If setTexture is going to be kept I think the name of the function to be improved to better reflect it's behavior -- like setStorageTexture or something and be documented.

[mrdoob]

@DavidPeicho FYI