- Original Message -
On Mon, 2013-02-11 at 20:47 +0100, srol...@vmware.com wrote:
From: Roland Scheidegger srol...@vmware.com
It looks like using coord.w as explicit lod value is a mistake, most likely
because some dx10 docs had it specified that way. Seems this was changed
On 11.02.2013 20:47, srol...@vmware.com wrote:
From: Roland Scheidegger srol...@vmware.com
It looks like using coord.w as explicit lod value is a mistake, most likely
because some dx10 docs had it specified that way. Seems this was changed
though:
Am 12.02.2013 08:06, schrieb Michel Dänzer:
On Mon, 2013-02-11 at 20:47 +0100, srol...@vmware.com wrote:
From: Roland Scheidegger srol...@vmware.com
It looks like using coord.w as explicit lod value is a mistake, most likely
because some dx10 docs had it specified that way. Seems this was
From: Roland Scheidegger srol...@vmware.com
It looks like using coord.w as explicit lod value is a mistake, most likely
because some dx10 docs had it specified that way. Seems this was changed though:
http://msdn.microsoft.com/en-us/library/windows/desktop/hh447229%28v=vs.85%29.aspx
- let's just
On Mon, 2013-02-11 at 20:47 +0100, srol...@vmware.com wrote:
From: Roland Scheidegger srol...@vmware.com
It looks like using coord.w as explicit lod value is a mistake, most likely
because some dx10 docs had it specified that way. Seems this was changed
though: