Marmoset Toolbag uses a somewhat customized shader language, which is a kind of union of HLSL and GLSL syntax conventions. This can be very helpful for development and debugging. Please note also that Toolbag’s console window (accessible through the Help -> Dev menu, or by pressing Ctrl + ~ on Windows and Cmd + Shift + C on Mac) will display any syntax errors during shader load or reload. There are also two example shaders included with Toolbag in the custom directory, and these provide good examples of common shading operations in Toolbag. Of particular note are mat.frag and ag, which will be discussed in more detail below. It’s worth exploring the contents of the mat directory as it contains source for the built-in shader modules in Toolbag, all of which are written in the same language and structure available to user shaders. User shaders belong in data/shader/mat/custom any files placed there will appear in the shader dropdown in the “Custom” material module as the tutorial video illustrates. Toolbag’s material shaders are located in the installation directory, inside data/shader/mat.

We suggest you give it a look before reading further: Some basic knowledge of shader development and languages will be helpful users looking to install custom shaders should see our Toolbag Add-On Library instead.įor those of you who might prefer a video introduction, our friend Chris Perrella has prepared a tutorial demonstrating the basics of custom shader creation and use. The purpose of this article is to provide enough of an introduction to get a developer or technical artist started.

This can be a powerful tool for users to extend Toolbag’s rendering capabilities, and for these improvements to be shared with others. Toolbag 3 provides a framework for users to customize the material shader system.

Nature soft occlusion shader unity