On Monday, 2018-06-18 13:07:12 +0200, Roland Scheidegger wrote:
> Am 18.06.2018 um 12:43 schrieb Eric Engestrom:
> > On Friday, 2018-06-15 23:38:58 +0200, srol...@vmware.com wrote:
> >> From: Roland Scheidegger
> >>
> >> The sampleMaskIn workaround (b936f4d1ca0d2ab1e828ff6a6e617f12469687fa)
> >> t
Am 18.06.2018 um 12:43 schrieb Eric Engestrom:
> On Friday, 2018-06-15 23:38:58 +0200, srol...@vmware.com wrote:
>> From: Roland Scheidegger
>>
>> The sampleMaskIn workaround (b936f4d1ca0d2ab1e828ff6a6e617f12469687fa)
>> tries to figure out if the shader is running at per-sample frequency, but
>>
On Friday, 2018-06-15 23:38:58 +0200, srol...@vmware.com wrote:
> From: Roland Scheidegger
>
> The sampleMaskIn workaround (b936f4d1ca0d2ab1e828ff6a6e617f12469687fa)
> tries to figure out if the shader is running at per-sample frequency, but
> there's a typo bug so it will only recognize per-samp
From: Roland Scheidegger
The sampleMaskIn workaround (b936f4d1ca0d2ab1e828ff6a6e617f12469687fa)
tries to figure out if the shader is running at per-sample frequency, but
there's a typo bug so it will only recognize per-sample linar inputs,
not per-sample perspective ones.
Spotted by Eric Engestr