On 09/13/2017 05:10 PM, Nicolai Hähnle wrote:
On 08.09.2017 16:42, Bas Nieuwenhuizen wrote:
On Fri, Sep 8, 2017 at 4:30 PM, Samuel Pitoiset
wrote:
On 09/08/2017 04:08 PM, Józef Kucia wrote:
On Fri, Sep 8, 2017 at 2:43 PM, Samuel Pitoiset
wrote:
when an application doesn't update the c
On 08.09.2017 16:42, Bas Nieuwenhuizen wrote:
On Fri, Sep 8, 2017 at 4:30 PM, Samuel Pitoiset
wrote:
On 09/08/2017 04:08 PM, Józef Kucia wrote:
On Fri, Sep 8, 2017 at 2:43 PM, Samuel Pitoiset
wrote:
when an application doesn't update the contents of a descriptor
set object, it contains r
On Fri, Sep 8, 2017 at 4:30 PM, Samuel Pitoiset
wrote:
>
>
> On 09/08/2017 04:08 PM, Józef Kucia wrote:
>>
>> On Fri, Sep 8, 2017 at 2:43 PM, Samuel Pitoiset
>> wrote:
>>>
>>> when an application doesn't update the contents of a descriptor
>>> set object, it contains random values and this might
On 09/08/2017 04:08 PM, Józef Kucia wrote:
On Fri, Sep 8, 2017 at 2:43 PM, Samuel Pitoiset
wrote:
when an application doesn't update the contents of a descriptor
set object, it contains random values and this might end up with
GPU VM faults if a shader tries to access that descriptor.
The Vu
On Fri, Sep 8, 2017 at 2:43 PM, Samuel Pitoiset
wrote:
> when an application doesn't update the contents of a descriptor
> set object, it contains random values and this might end up with
> GPU VM faults if a shader tries to access that descriptor.
>
> The Vulkan spec doesn't state what a driver s
when an application doesn't update the contents of a descriptor
set object, it contains random values and this might end up with
GPU VM faults if a shader tries to access that descriptor.
The Vulkan spec doesn't state what a driver should do when
a descriptor is unset, but zeroing the contents see
