Skip to content

Conversation

@WestLangley
Copy link
Collaborator

Because of the familiar warning

don't use render targets as textures. Use their .texture property instead.

we now pass renderTarget.texture instead of renderTarget itself.

Thing is, in passing the texture, we have no access to the texture dimensions, which are properties of the render target.

This PR uses the same approach as is used with DataTexture to solve this problem.

@mrdoob mrdoob added this to the r106 milestone Jun 2, 2019
@mrdoob mrdoob merged commit 297551d into mrdoob:dev Jun 2, 2019
@mrdoob
Copy link
Owner

mrdoob commented Jun 2, 2019

Thanks!

@WestLangley WestLangley deleted the dev_render_target branch June 2, 2019 16:35
jsantell added a commit to jsantell/three.js that referenced this pull request Jun 17, 2019
…return an empty string if a data URL cannot be generated. Allows the serialization of a scene with a DataTexture/WebGLRenderTarget after mrdoob#16651 landed without throwing. Fixes mrdoob#16763.
jsantell added a commit to jsantell/three.js that referenced this pull request Aug 23, 2019
…return an empty string if a data URL cannot be generated. Allows the serialization of a scene with a DataTexture/WebGLRenderTarget after mrdoob#16651 landed without throwing. Fixes mrdoob#16763.
jsantell added a commit to jsantell/three.js that referenced this pull request Aug 23, 2019
…return an empty string if a data URL cannot be generated. Allows the serialization of a scene with a DataTexture/WebGLRenderTarget after mrdoob#16651 landed without throwing. Fixes mrdoob#16763.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants