[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Re: WebGL spec modifications for D3D
On Wed, Jul 14, 2010 at 11:40 AM, Daniel Koch <email@example.com> wrote:
> Hi folks,
> We've discussed this further with Google off-list and believe that best way
> forward is to leave the invariance language from GLSL ES in WebGL as
> suggested. OpenGL implementations will be able to use it as normal and
> ANGLE will rely on the invariance guarantees that are provided by D3D9 and
> HLSL. We'll continue to investigate what invariance guarantees are
> available in D3D9 and what we may be able to do should any applications
> which demonstrate invariance issues on ANGLE arise.
Based on these discussions, I've removed the section from the spec
which stated that the invariant keyword is ignored in WebGL. If this
should have been done differently (for example relaxing the language
in the spec rather than removing it entirely) please post.
> Hope this helps,
> On 2010-07-14, at 12:06 PM, Chris Marrin wrote:
> On Jul 13, 2010, at 12:29 PM, Daniel Koch wrote:
> Hi folks,
> The problem is that there is nothing like the "invariant" keyword in D3D9
> HLSL (or even D3D10 HLSL for that matter) that I am aware of.
> In practise, there must be some form of invariance guaranteed by d3d9
> (especially for position), since I know of many games which use multi-pass
> rendering algorithms which work just fine. The difficulty lies in figuring
> out exactly what is guaranteed by D3D9, since we've been unable to find any
> sort of public documentation or discussion of these issues. However, even
> if there is position invariance, this does not provide a mechanism to toggle
> invariance on and off on a per-variable basis as is required in GLSL.
> I think we certainly need the feature of invariance. Perhaps D3D always
> creates invariant shaders (it never does optimizations that would break
> invariance)? If so, then I suggest we keep the keyword, use it normally in
> OpenGL implementations (where supported) and ignore it in HLSL. Of course, I
> haven't investigated the issue, so I'm not sure if this is possible. But I
> believe we need to:
> a) Make it possible to guarantee an invariant shader
> b) Make it possible to enable and disable invariance in implementations that
> support it.
> Daniel Koch -+- firstname.lastname@example.org -+- 1 613.244.1111 x352
> Senior Graphics Architect -+- TransGaming Inc. -+- www.transgaming.com
> 311 O'Connor St., Suite 300, Ottawa, Ontario, Canada, K2P 2G9
> This message is a private communication. It also contains information that
> is privileged or confidential. If you are not the intended recipient, please
> do not read, copy or use it, and do not disclose it to others. Please
> notify the sender of the delivery error by replying to this message, and
> then delete it and any attachments from your system. Thank you.
You are currently subscribed to email@example.com.
To unsubscribe, send an email to firstname.lastname@example.org with
the following command in the body of your email: