On 23/04/15 00:06, srol...@vmware.com wrote:
From: Roland Scheidegger
We were resetting the prim id count for each run of the prim assembler,
hence this only worked when the draw calls were very small (the exact limit
depending on the vertex size), since larger draw calls get split up.
So, do t
Am 23.04.2015 um 02:35 schrieb Matt Turner:
> On Wed, Apr 22, 2015 at 4:06 PM, wrote:
>> From: Roland Scheidegger
>>
>> We were resetting the prim id count for each run of the prim assembler,
>> hence this only worked when the draw calls were very small (the exact limit
>> depending on the verte
On Wed, Apr 22, 2015 at 4:06 PM, wrote:
> From: Roland Scheidegger
>
> We were resetting the prim id count for each run of the prim assembler,
> hence this only worked when the draw calls were very small (the exact limit
> depending on the vertex size), since larger draw calls get split up.
> So
From: Roland Scheidegger
We were resetting the prim id count for each run of the prim assembler,
hence this only worked when the draw calls were very small (the exact limit
depending on the vertex size), since larger draw calls get split up.
So, do the same as we do already if there's a gs, reset