Re: [Public WebGL] WebGL Antialiasing

Subject: Re: [Public WebGL] WebGL Antialiasing

From: Florian Bösch <pyalot@gmail.com>

Date: Sat, 24 Nov 2012 13:16:16 +0100

Cc: public webgl <public_webgl@khronos.org>

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BmDDay2uODs4hEit062f7DB8P0E15q7oWk9tTr7Kk3s=; b=Qhfmd1vAfVb/R3jnuP2avlibGq/O3cQFHXxe2MwO5KR5+kCWvuEtr3xB2dcLa5W2HY LrUk+K8VgXJVQ1c15iBIGU56P5HyLgtxcQSilZC7Vogs3BzHcvN3qMS2VdbB2+tAWDDR HmTt6N1YucZnelgi8vkgM6Ar2zpLgPIhXpiGWskAYkXMdzNsLpXlbNaVP+UUG3owbK7T 5k2JEF9rbQMT07aMc6DVso4NhsbLPQm9WKiBxXMKNjnenAnXhUkI49rSLtsrmzSXIUHL 2nC5HfTZVc0zUOMm4Aerd5diBnv9NUD9DkoqJqEge9exakeuThPTt84G3sYJrOW1pQQ1 qwJQ==

In-reply-to: <7DAAA5E6-83AD-4FD5-AD44-E2AEF8D1DAD8@acko.net>

List-archive: <https://www.khronos.org/webgl/public-mailing-list/archives/>

List-id: Public COLLADA Mailing List <public_webgl.khronos.org>

List-owner: <mailto:owner-public_webgl@khronos.org>

List-post: <mailto:public_webgl@khronos.org>

List-subscribe: <mailto:majordomo@khronos.org?body=subscribe%20public_webgl>

List-unsubscribe: <mailto:majordomo@khronos.org?body=unsubscribe%20public_webgl>

References: <7DAAA5E6-83AD-4FD5-AD44-E2AEF8D1DAD8@acko.net>

Sender: owner-public_webgl@khronos.org

- Why is the flag considered a request which may be ignored?

Because anti-aliasing may not be available.

- Why are you incapable of inspecting or controlling the applied quality level of MSAA?

- Why are you incapable of checking if the request has been satisfied?

Because this is not a GL API. It's a non standardized function of the underlying window manager, so it hasn't been specced, added or implemented in the context of a GL specification.

At the very least, WebGL developers should have the ability to detect whether antialiasing can actually be applied and to what degree.

The UA folks usually worry about adding more machine specific bits that can identify users.

That is, how many color/depth/stencil samples, how many coverage samples, etc. That way, if the native implementation is insufficient, they can replace it with a custom post-processing filter, possibly in combination with super-resolution rendering. I could easily see myself doing a quick off-screen rendering benchmark to determine optimal settings. Right now I can't, because I'm working blind.

I would be in favor of something that lets us take finer control of aliasing and query its quality parameters.

References:

[Public WebGL] WebGL Antialiasing
- From: Steven Wittens <steven@acko.net>