Am 17.07.2015 um 16:18 schrieb Brian Paul:
> On 07/16/2015 03:15 PM, srol...@vmware.com wrote:
>> From: Roland Scheidegger
>>
>> In particular, we were incorrectly accepting s3tc (and lots of others)
>> for CompressedTexSubImage3D (but not CompressedTexImage3D) calls with 3d
>> targets. At this ti
Am 17.07.2015 um 16:18 schrieb Brian Paul:
> On 07/16/2015 03:15 PM, srol...@vmware.com wrote:
>> From: Roland Scheidegger
>>
>> In particular, we were incorrectly accepting s3tc (and lots of others)
>> for CompressedTexSubImage3D (but not CompressedTexImage3D) calls with 3d
>> targets. At this ti
On 07/16/2015 03:15 PM, srol...@vmware.com wrote:
From: Roland Scheidegger
In particular, we were incorrectly accepting s3tc (and lots of others)
for CompressedTexSubImage3D (but not CompressedTexImage3D) calls with 3d
targets. At this time, the only allowed formats for these calls are the
bptc
On 07/16/2015 03:15 PM, srol...@vmware.com wrote:
From: Roland Scheidegger
In particular, we were incorrectly accepting s3tc (and lots of others)
for CompressedTexSubImage3D (but not CompressedTexImage3D) calls with 3d
targets. At this time, the only allowed formats for these calls are the
bptc
From: Roland Scheidegger
In particular, we were incorrectly accepting s3tc (and lots of others)
for CompressedTexSubImage3D (but not CompressedTexImage3D) calls with 3d
targets. At this time, the only allowed formats for these calls are the
bptc ones, since none of the specific extensions allow i