To add a new shader generator for a target you add a new C++ class derived from the base class ShaderGenerator, or one of the existing derived shader generator classes ( GlslShaderGenerator, OslShaderGenerator, etc.), and override the methods you need to customize. Hence a separate shader generator can be defined for each language/target combination.Ĭlass inheritance and specialization is used to create support for new languages or to customize existing language support for a new target.
Another example is different renderers supporting OSL but with different sets of closures or closure parameters. For example OpenGL renderers supporting GLSL can use forward rendering or deferred rendering, each with very different requirements for how the shaders are constructed. However for each language there can also be variations needed for different renderers. There is one shader generator for each supported shading language. The MaterialX description is free from device specific details and all implementation details needs to be taken care of by shader generators. See Figure 1 for a high level overview of the system.įigure 1: Shader generation with multiple shader generators. The source code produced needs to be compiled by a shading language compiler before being executed by the renderer. Note that this system has no runtime and the output produced is source code, not binary executable code. A library module named MaterialXGenShader contains the core shader generation features, and support for specific languages resides in separate libraries, e.g. This can help applications to transform the agnostic MaterialX data description into executable shader code for a specific renderer. A shader generation framework is implemented as part of MaterialX.
0 kommentar(er)
