On 10/25/2017 09:54 AM, Roland Scheidegger wrote:
Am 25.10.2017 um 16:57 schrieb Roland Scheidegger:
Am 25.10.2017 um 16:29 schrieb Brian Paul:
On 10/24/2017 07:06 PM, srol...@vmware.com wrote:
From: Roland Scheidegger
These assertions were revisited a couple of times in the past, and they
s
Am 25.10.2017 um 16:57 schrieb Roland Scheidegger:
> Am 25.10.2017 um 16:29 schrieb Brian Paul:
>> On 10/24/2017 07:06 PM, srol...@vmware.com wrote:
>>> From: Roland Scheidegger
>>>
>>> These assertions were revisited a couple of times in the past, and they
>>> still weren't quite right.
>>> The p
Am 25.10.2017 um 16:29 schrieb Brian Paul:
> On 10/24/2017 07:06 PM, srol...@vmware.com wrote:
>> From: Roland Scheidegger
>>
>> These assertions were revisited a couple of times in the past, and they
>> still weren't quite right.
>> The problem I was seeing (with some other state tracker) was a c
On 10/24/2017 07:06 PM, srol...@vmware.com wrote:
From: Roland Scheidegger
These assertions were revisited a couple of times in the past, and they
still weren't quite right.
The problem I was seeing (with some other state tracker) was a copy between
two 512x512 s3tc textures, but from mip level
From: Roland Scheidegger
These assertions were revisited a couple of times in the past, and they
still weren't quite right.
The problem I was seeing (with some other state tracker) was a copy between
two 512x512 s3tc textures, but from mip level 0 to mip level 8. Therefore,
the destination has on
