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

EX9.Dataflow

French | Italian

The overall dataflow of the 3d rendering pipeline in vvvv looks as follows:

vvvv passes several data to the graphics card:

  • Mesh
  • Texture
  • User defined variables
  • Render Sates
  • Transform matrices

First the vertexshader programm is applied to each vertex. Its major task is to project the geometry onto the screen. The output is the vertex position in screenspace for the rasterizer and other data for the pixel shader.

Between vertexshader and pixelshader the conversion from vector graphics to pixel graphics happens. This is done by the rasterizer, that calculates which screen pixels belong to the geometry. It also interpolates per-vertex data sent from the vertex shader to per-pixel data for pixels which lie between the vertices.

Then the pixelshader programm is executed for every visible pixel, as defined by the rasterizer. It calculates the final color of the pixel.

anonymous user login

Shoutbox

~7h ago

Urbankind: circuitb:Wrongcop is epic! :)

~8h ago

joreg: @tobi: use GetSlice() as the patch i referred you to is demonstrating. or start a forum thread with your patch.

~8h ago

TobiTobsen123: hmm yes i can see the values...but how to handle them as seperate values? I need to forward them via TCP/IP...

~9h ago

joreg: @tobi: OSCDecoder helppatch has a section: OSC_Advanced (bottomright) that demoes decoding of multiple messages

~10h ago

TobiTobsen123: I'm using an OSCDecoder, it receives two arguments...works but how can I seperate the arguments into two seperate values

~12h ago

u7angel: @mediadog, make it a forum question.

~12h ago

u7angel: @mediadog, tty renderer ?

~15h ago

microdee: however non-conductive objects are invisible for this so the pencil and the sticks in the video are still a mysteries