On 08/22/2012 03:21 PM, Eric Anholt wrote:
> Paul Berry writes:
>
>> On 22 August 2012 12:35, Eric Anholt wrote:
>>
>>> Paul Berry writes:
>>>
Previously, when performing a fast depth clear, we would also clear
the miptree's resolve map. This destroyed important information,
sin
Paul Berry writes:
> On 22 August 2012 12:35, Eric Anholt wrote:
>
>> Paul Berry writes:
>>
>> > Previously, when performing a fast depth clear, we would also clear
>> > the miptree's resolve map. This destroyed important information,
>> > since the resolve map contains information about neede
On 22 August 2012 12:35, Eric Anholt wrote:
> Paul Berry writes:
>
> > Previously, when performing a fast depth clear, we would also clear
> > the miptree's resolve map. This destroyed important information,
> > since the resolve map contains information about needed resolves for
> > all levels
Paul Berry writes:
> Previously, when performing a fast depth clear, we would also clear
> the miptree's resolve map. This destroyed important information,
> since the resolve map contains information about needed resolves for
> all levels and layers of the miptree, whereas a depth clear only
>
Previously, when performing a fast depth clear, we would also clear
the miptree's resolve map. This destroyed important information,
since the resolve map contains information about needed resolves for
all levels and layers of the miptree, whereas a depth clear only
applies to a single level/layer
