This operator lets you write VEX code that is put directly into your shader or operator definition.

Up to 64 inputs can be connected to this operator, and they can be of any data type. You can also use the parameters of this operator to define up to 32 outputs that can also be of any data type, and be given any name.

When writing your inline VEX code, you do not need to write variable declarations for any of the inputs or outputs to the operator. Any extra variables that you do declare should be prefixed with a $. This tells the VOPNET code generator that it is a variable name, and should be made unique. Similarly, when referring to input or output variables, their names should be prefixed with a $, or the code generator will not use the correct variable names. Do not use the $ prefix for global variable names.

The $ is needed if you are going to instantiate more than one copy of your VOP in the same shader. Without the $ before variable names, the variables will be declared with the same name in different Inline VOPs, resulting in the same value being referenced in each VOP. This sharing of values between VOPs is normally not wanted, so the $ makes a new version of the declared variable in each instance of the VOP.

Although it is possible to assign values to input variables, it is strongly discouraged. There is no guarantee made about the order in which VOPs will generate their code, so assigning values to input variables may give unpredictable results.

You should use this operator only if you are familiar with VEX programming. It is very easy to introduce errors into your code using this operator. If there are errors in your code, you will be able to see what they are by middle-clicking on the icon of any VOP in the network.

As an example, the following inline code will output the length of the hypotenuse of a right angle triangle, if the Inline VOP node has two inputs named in1 and in2 and an output named out1:

$out1 = sqrt($in1 * $in1 + $in2 * $in2);