[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] meaning of the specification of FBO sampling and interpretation by UAs

Definitely the latter.  If a texture is not sampled, there is no
reason to generate an error. Since ANGLE shader translator provides
enough information what textures are actually sampled (or at least a
close estimation, if a sampler is defined and statically accessed), we
can have a more refined behavior.

This seems to be a behavior difference between Chrome's GPU command
buffer and ANGLE, and we should fix the ANGLE behavior.

On Sun, Mar 19, 2017 at 2:05 PM, Florian Bösch <pyalot@gmail.com> wrote:
> The ES specification states that the result of sampling from a texture
> attached to a framebuffer at the same time as sampling to that framebuffer
> is undefined.
> Google chrome seems to interprete this as: If a texture is bound to any
> texturing unit while that framebuffer is used it's an error.
> However a different interpretation of this would be: If a texture that is
> bound is actually sampled during the framebuffer operation it's an error.
> Which of these interpretations is the correct one?

You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl