Save resources by not binding a color texture to a render target #12455
Conversation
|
Please make sure to tag your PR with "bug", "new feature" or "breaking change" tags. |
|
Please make sure to tag your PR with "bug", "new feature" or "breaking change" tags. |
|
Snapshot stored with reference name: Test environment: To test a playground add it to the URL, for example: https://babylonsnapshots.z22.web.core.windows.net/refs/pull/12455/merge/index.html#WGZLGJ#4600 Links to test babylon tools with this snapshot: https://playground.babylonjs.com/?snapshot=refs/pull/12455/merge To test the snapshot in the playground with a playground ID add it after the snapshot query string: https://playground.babylonjs.com/?snapshot=refs/pull/12455/merge#BCU1XR#0 |
This PR allows the user to indicate that the color texture should not be created/bound when creating a render target.
It's a waste of resources (a texture the size of the render target) if all you want is generating the depth buffer/texture and don't have anything to write in a color texture.
Here's a PG to test it: https://playground.babylonjs.com/#0PYWXZ#1
With Spector, you will see that only the depth buffer is bound:
Without the PR, a color texture is also bound:
