arijan

Thanks, I removed quad shifting part in my engine . However that didn`t solve my issue , which means it is something
different from the topic I started

Thanks anyway

Tanzanite , thanks a lot for all your help ,

things are clear in my side now

and as for my struct usage ofcourse I am not going to use rgb stuff inside structs like this , it was just for example.

By the way as I have tested , I can use in out with structs so that I can share structs between shader stages.
But I am trying to understand its pros and cons against non-uniform in/out interface blocks :

// inside the vertex shader
out struct test
{
ATTRIB(0) float red;
ATTRIB(1) float green;
ATTRIB(2) float blue;
} ;
test v_out;

But I think that is working because I use I declare a global variable with that struct type ?

Firstly I have an AMD card.

1. I am not supposed to use in/out qualifiers with structs ? Does that mean if I am going to share things between stages
they should be either interfaces or just global variables using in/out qualifiers ?

2. In HLSL side, I am using semantics like TEXCOORD4_centroid , and I was planning to use something like
layout(location=4) to match TEXCOORDs. And at the same time I want to specify that that variable should be sampled by
centroid sampling method

How can I achieve this ?

3. Regarding mixing `in centroid` with an `out struct` ,I was trying the code above in a vertex shader so that I want to output that struct and that is working like that.
On the other hand the compiler doesn`t allow me to use centroid with out in a vertex shader but it just allows `centroid in` in a vertex shader.

Is the site really rubbish ?


I really am looking forward to hearing feedbacks , especially constructive ones


thanks...