On 12/08/16 02:14, Timothy Arceri wrote:
> On Thu, 2016-08-11 at 17:10 +0200, Alejandro Piñeiro wrote:
>> On 05/08/16 12:20, Alejandro Piñeiro wrote:
>>> On 05/08/16 01:53, Timothy Arceri wrote:
On Thu, 2016-08-04 at 18:36 +0200, Alejandro Piñeiro wrote:
> Hi,
>
> these days I have
On Thu, 2016-08-11 at 17:10 +0200, Alejandro Piñeiro wrote:
> On 05/08/16 12:20, Alejandro Piñeiro wrote:
> >
> > On 05/08/16 01:53, Timothy Arceri wrote:
> > >
> > > On Thu, 2016-08-04 at 18:36 +0200, Alejandro Piñeiro wrote:
> > > >
> > > > Hi,
> > > >
> > > > these days I have been trying to
On 05/08/16 12:20, Alejandro Piñeiro wrote:
> On 05/08/16 01:53, Timothy Arceri wrote:
>> On Thu, 2016-08-04 at 18:36 +0200, Alejandro Piñeiro wrote:
>>> Hi,
>>>
>>> these days I have been trying to fix a test that uses transform
>>> feedback
>>> on the out varying of a tessellation shader. The rel
On 05/08/16 01:53, Timothy Arceri wrote:
> On Thu, 2016-08-04 at 18:36 +0200, Alejandro Piñeiro wrote:
>> Hi,
>>
>> these days I have been trying to fix a test that uses transform
>> feedback
>> on the out varying of a tessellation shader. The relevant part on
>> that
>> shader is like this:
>>
>>
On Thu, 2016-08-04 at 18:36 +0200, Alejandro Piñeiro wrote:
> Hi,
>
> these days I have been trying to fix a test that uses transform
> feedback
> on the out varying of a tessellation shader. The relevant part on
> that
> shader is like this:
>
> layout (vertices=4) out;
>
> out block { ve
Hi,
these days I have been trying to fix a test that uses transform feedback
on the out varying of a tessellation shader. The relevant part on that
shader is like this:
layout (vertices=4) out;
out block { vec4 value; } user_out[];
The test tries to use block.value as the varying name whe
