Effect language

Create shaders in C

ShaderSource objects. Shaders come in three types:

• ShaderClassSource correspond to a unique shader class
• ShaderMixinSource mix several ShaderSource, set preprocessor values, define compositions
• ShaderArraySource are used for arrays of compositionsThis method produces shaders at runtime. However, many platforms don’t support HLSL and have no ability to compile shaders at runtime. Additionally, the approach doesn’t benefit from the reusability of mixins.

  Xenko Effects (XKFX)

  Many shaders are variations or combinations of pre-existing shaders. For example, some meshes cast shadows, others receive them, and others need skinning. To reuse code, it’s a good idea to select which parts to use through conditions (eg “Skinning required”). This is often solved by “uber shaders”: monolithic shaders configured by a set of preprocessor parameters. Xenko offers the same kind of control, keeping extensibility and reusability in mind. The simple code blocks defined by shader classes can be mixed together by a shader mixer. This process can use more complex logic, described in Xenko Effect (*.xkfx) files.

  General syntax

  ShaderMixinSource ready to be compiled. An example .xkfx file:

  using Xenko.Effects.Data;namespace XenkoEffects{    params MyParameters    {        bool EnableSpecular = true;    };    effect BasicEffect    {        using params MaterialParameters;        using params MyParameters;        mixin ShaderBase;        mixin TransformationWAndVP;        mixin NormalVSStream;        mixin PositionVSStream;        mixin BRDFDiffuseBase;        mixin BRDFSpecularBase;        mixin LightMultiDirectionalShadingPerPixel<2>;        mixin TransparentShading;        mixin DiscardTransparent;        if (MaterialParameters.AlbedoDiffuse != null)        {            mixin compose DiffuseColor = ComputeBRDFDiffuseLambert;            mixin compose albedoDiffuse = MaterialParameters.AlbedoDiffuse;        }        if (MaterialParameters.AlbedoSpecular != null)        {            mixin compose SpecularColor = ComputeBRDFColorSpecularBlinnPhong;            mixin compose albedoSpecular = MaterialParameters.AlbedoSpecular;        }    };}

  Add a mixin

  mixin <mixin_name>.

  Use parameters

  The syntax is similar to C#. The following rules are added:
• params <shader_name>. If you don’t, keys are treated as variables.
• You don’t need to tell the program where to check the values behind the keys. Just use the key.

  using params MaterialParameters;if (MaterialParameters.AlbedoDiffuse != null){    mixin MaterialParameters.AlbedoDiffuse;}

  The parameters behave like any variable. You can read and write their value, compare their values, and set template parameters. Since some parameters store mixins, they can be used for composition and inheritance, too.

  Custom parameters

  You can create your own set of parameters using a structure definition syntax.

  Note

  using statement when you want to use them.

  params MyParameters{    bool EnableSpecular = true; // true is the default value}

  Compositions

  To add a composition, assign the composition variable to your mixin with the syntax below.

  // albedoSpecular is the name of the composition variable in the mixinmixin compose albedoSpecular = ComputeColorTexture;ormixin compose albedoSpecular = MaterialParameters.AlbedoSpecular;

  Partial effects

  You can also break the code into sub-mixins to reuse elsewhere with the syntax below.

  partial effect MyPartialEffect{    mixin ComputeColorMultiply;    mixin compose color1 = ComputeColorStream;    mixin compose color2 = ComputeColorFixed;}// to use itmixin MyPartialEffect;mixin compose myComposition = MyPartialEffect;

  MyPartialEffect mixin like any other mixin in the code.

  See also

• Shading language