» EX9.Effect.Template
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

EX9.Effect.Template

French | Italian | Spanish

The Template has the whole effect structure already laid out as code and implements the most basic and working vertex- and pixel-shader. In fact a constant shading with simple texturing.

The template is structured in 4 sections:

  • Parameters
  • VertexShader
  • PixelShader
  • Techniques

Parameter

In the parameter section it first declares the most commonly used transformation matrices via semantics. Note that the variable tW which is declared with the WORLD semantic appears as a pin on the effect, while the other transformations do not. The VIEW and PROJECTION semantics assign the respective matrices that are connected to the Renderer (EX9)s View Transform and Projection Transform to the tV and tP matrices.

Next it declares a texture and a sampler, which has this texture assigned. The last parameter is the texture transformation matrix.

For every effect you also have to specify which data you want to output from the vertexshader and receive as parameter in the pixelshader. This is most conveniently done via a struct:

struct vs2ps
{
    float4 Pos  : POSITION;
    float2 TexCd : TEXCOORD0;
};

Note that this very struct is used as a return parameter for the vertexshader function:

vs2ps VS(float4 PosO  : POSITION, float4 TexCd : TEXCOORD0)
 {..}

and also as the parameter input to the pixelshader function:

float4 PS(vs2ps In): COLOR
 {..}

Using a struct like here is not mandatory. Besides the struct you can pump additional parameters into the pixelshader function as you like.

In this simple case the struct only carries two values: The position and texture coordinate vectors. In a realworld effect you'll very likely pass more information from the vertex- to the pixelshader.

VertexShader

The templates vertexshader function does not very much. It only fills the output struct with the current vertex position in projection space:

 Out.Pos = mul(PosO, tWVP);

and the current vertex texture coordinate transformed via the input texture transformation matrix:

 Out.TexCd = mul(TexCd, tTex);

PixelShader

The pixelshader function is even simpler. It takes the incoming texture coordinate for this pixel to get the color of the sampler Samp at this position and returns it.

Techniques

The template effect specifies two techniques. TSimplShader is the cool one, using the shader functions. The other is boring using only fixed function instructions, which you most likely will not need.

anonymous user login

Shoutbox

~19h ago

joreg: Two #vvvv workshops this week in #berlin: Friday: Physical Computing, Saturday: Computer Vision. Tickets: upcoming-full-day-vvvv-gamma-workshops-in-berlin

~1d ago

joreg: @cznickesz also feel free to join our chat for such questions: chat

~1d ago

cznickesz: @joreg: Yeah, I´ll give it a try! Thx

~1d ago

joreg: @cznickesz: we're hoping this week. but depends on feedback. please test your project and let us know if it works.

~2d ago

cznickesz: @joreg: I should stop asking my questions so cryptic ;-) So right away: is final Beta39 hours, days or weeks away?

~2d ago

joreg: @cznickesz: the idea of an RC is exactly to make sure your projects will work with it. your last chance to report problems with b39.

~2d ago

cznickesz: So how "RC" is the "RC3"? I have to update an old project soon and I´m wondering if I should wait and directly update to Beta39

~2d ago

joreg: @takuma, the "one frame" issue was fixed in RC3 for beta39, see: beta39-release-candidate

~2d ago

Takuma: @joreg thank!! Ill try this. Are there a way to send video texture from vvvv to vl? fromimage node in vl somehow only sends 1 frame

~2d ago

cznickesz: @ravasquez thx, so I need to stop avoiding nuget in the end ;-)