Closed GoogleCodeExporter closed 9 years ago
We considered allowing this when we were dealing with the feedback loops in the
past but decided against it because we didn't want anyone relying on this
unspecified behavior.
With our D3D9 backend, it was possible to bind the current color buffer as a
sampler to read and write simultaneously but a lot of WebGL samples stopped
working when our D3D11 backend became more popular because users started
relying on the feedback loop working. We had the WebGL spec amended and it now
generates an error in this case. If possible, we'd like to keep the behaviour
consistent between our renderers.
Original comment by geofflang@chromium.org
on 23 Jan 2015 at 3:41
Ok, thanks for the clarification.
Original comment by Gregory....@imgtec.com
on 23 Jan 2015 at 3:44
Original comment by geofflang@chromium.org
on 3 Feb 2015 at 4:55
Original issue reported on code.google.com by
Gregory....@imgtec.com
on 23 Jan 2015 at 3:26