With the recent inclusion of texture arrays into fast_graph (e119c910cc3f047aa91697bc25de99f428620374), the sampler api no longer is just passing 2D image URIs around and a special case for RenderNodes. The compositing system also adds a bit of complexity over scheduling indirect rendering, and so there are a number of cases where things should work but probably don't and there is no test coverage to say for sure. #161 / #251 will likely add more complexity.
This issue should amount to adding automated tests to cover these cases, and then fix whatever seems broken. Hopefully the existing framework should be sufficient and this should not depend on completing #248.
Some cases to consider:
[ ] Compositor's handling of GraphNodes with RenderNodes for textures
[ ] Compositor's handling of GraphNodes with texture arrays containing RenderNodes
With the recent inclusion of texture arrays into fast_graph (e119c910cc3f047aa91697bc25de99f428620374), the sampler api no longer is just passing 2D image URIs around and a special case for RenderNodes. The compositing system also adds a bit of complexity over scheduling indirect rendering, and so there are a number of cases where things should work but probably don't and there is no test coverage to say for sure. #161 / #251 will likely add more complexity.
This issue should amount to adding automated tests to cover these cases, and then fix whatever seems broken. Hopefully the existing framework should be sufficient and this should not depend on completing #248.
Some cases to consider: