Community

Question

Essentially what the title says. When writing CG programs, the Unity docs say to create the texcoords in a structure as a float4. What is stored in the zw components?

//example
struct v2f {
    float4 texcoord : TEXCOORD0;
};

when most of the time I just use the xy components.

EDIT: I just looked at the CG documentation page, and it looks like it stores texcoords as a float2 in every example that I looked at.

Answer 1

0

Graphics cards use float4's to store and manipulate everything. They literally don't have simple variables in their chips or have simple math circuits. You ask one to add 4+7, it gets confused, then prints, "oh, you mean (4,0,0,0) plus (7,0,0,0)!!."

For UV's the 3rd is the 3rd dimension (if you have 64 textures, all 64x64, you can think of the 3rd as picking/blending which textures to use.) The 4th is the scale factor (backwards: 2 is one half size.) They are always (0,1.)

But, the lookup command is generally tex2D(texture, i.texcoords.xy); so the last two aren't even used.

I personally use float2s for UVs, but a float2 is really a float4 with the last two slots taped over, and saves 0 time over using a float4. Most likely someone just typed float4 way back and there was never a reason to change it.

answered Mar 19 '11 at 08:18 PM

Owen Reynolds
11.3k ● 1 ● 7 ● 45

So, are all numerical data types created "implicitly" as 4 component vectors?

Mar 20 '11 at 02:46 AM Peter G

If you look at the Terrain shader, the blend weights of the 1st four textures are packed into one float4 instead of being sent over in four floats. One of the tricks is that you use float2 animals; with x for cats and y for dogs, to save space. You can say animals+=float2(1,5); to add 1 cat and 5 dogs, and it runs faster than cats+=1; dogs+=5;.

Mar 20 '11 at 03:12 AM Owen Reynolds

What about, say, multiplications of two vectors? Is it really not faster to multiply a vec2 rather than a vec4?

Mar 20 '11 at 03:21 AM Jessy

The GPU math circuits are made by welding four "normal" math units side-by-side. They take two float4's as input, and give a float4 as output. In a normal CPU, float2's don't really exist -- it adds them using two normal adds, one after another, so of course adding 4 is slower. Think of a car that seats 4.

Mar 20 '11 at 04:50 PM Owen Reynolds

Thanks for the detailed explanation.

Mar 20 '11 at 06:26 PM Peter G

show 3 more replies

(comments are locked)

Answer 2

0

After conducting a little more experimentation, Unity will let you create the texcoords as a float2.

//this is also valid:
struct v2f {
    float2 texcoord : TEXCOORD0;
};

Owenpat does a nice job explaining why the Unity docs recommends creating them as a float4 instead though.

answered Mar 20 '11 at 06:30 PM

Peter G
15k ● 16 ● 44 ● 136

(comments are locked)

Answer 3

0

that's pretty cool

answered Jun 10 '11 at 12:05 AM

spongyzetaprime
0 ● 6 ● 8 ● 13

Please, don't post comments as answers.

Jul 04 '11 at 01:36 PM Paulius Liekis

(comments are locked)

Community

Why are texcoords (uvs) stored in float4?

Follow this question

Welcome to Unity Answers

Unity Answers tutorial video!

Related Questions