Shader Master (Node Editor for Custom Shaders)

[SpiderPig]

Thought I'd show off my node editor for Ultra Engine Shaders.  Currently I'm developing it as I develop my game, so features get added as I need them.  But I'd love to hear your feedback and if you'd like me to add something I'm sure I can oblige.

Discord for ShaderMaster

ShaderMaster_v1.3.zip

Before use, you need to set the path to UltraEngine like this so it can find the tools and shaders.  You will also need to copy 'FragmentCustom.glsl' to 'UltraEngine\Templates\Common\Source\Shaders\PBR' in order to use the fragment shader nodes.

Then to create a new project go to File->New Project and enter in a name.  PBR is the only available at the moment and you can choose PostEffect from the right drop down - but this has not been tested in some time!  Feel free to explore it though.

Add a file to the project by clicking the file icon with the '+'.  Below are the files associated with one of my projects.  Macros are also visible when the checkbox is checked.  Macros are functions that can be used between projects.  Create a function, right click the function file and choose 'Convert to Macro'.  The function will be removed the current project and added to the macro folder.

 

Choose a file type, this is either a shader stage or a function or definition.  I've used the fragment shader extensively.  I have used the vertex and geometry shaders though there may be bugs here.  Please let me know.  Tessellation and Compute stages aren't working yet.

 

Select a file from the list on the right to open it and right click in the node area to get a menu of all the available nodes.

I'll make in depth tutorials on this later if any one is interested as there's a lot more to cover.  Right now it's there to play with.

An example of the fragment shader for my voxel terrain.

[Josh]

I'm implementing the new flowgraph editor now. I am going to try to make 'Flowgraph" and "FlowgraphNode" as custom widgets so maybe you can use them if you want.

[SpiderPig]

Still churning away at this.  Working on the geometry shader at the moment and custom outputs.

[Yue]

Is that for leadwerks?

[SpiderPig]

It's for Ultra.  Not sure if I'll make it work for Leadwerks yet.

[SpiderPig]

Updated start of the thread with a download to try.

[SpiderPig]

While there is no viewer in the shader editor (probably will be once Ultra supports C#) you can create a file watcher in your application to watch the changes you make in real-time.  Within a second or two

Add this at the start of your program.

auto watcher = CreateFileSystemWatcher("Materials");

And add this to your loop.

while (PeekEvent()) {
    auto ev = WaitEvent();

    if (ev.id == EVENT_FILECHANGE or ev.id == EVENT_FILECREATE)
    {
        //Look for a loaded asset with this file path
        auto asset = FindCachedAsset(ev.text);
        if (asset)
        {
            //Reload the modified asset
            if (asset->As<Material>() != nullptr) {
                auto material = asset->As<Material>();
                vector<shared_ptr<Texture>> textures;
                for (int id = 0; id < 16; id++) {
                    auto tex = material->GetTexture(id);
                     textures.push_back(tex);
                }
                asset->Reload();

                //If you assign textures progmatically you need to do this to make sure the newly loaded material has them too.
                material = asset->As<Material>();
                for (int id = 0; id < 16; id++) {
                material->SetTexture(textures[id], id);
                }
            }
            else {
                asset->Reload();
            }
        }
    }
}

You can also setup the shader project to automatically compile and export to multiple projects that may use it.

In 'Preferences' under 'Export Options' you can browse to any one of your Ultra projects and add them to the list.  This list will be saved between any shader project.  You then need to check which Ultra project you want the shader to be exported to and then check 'Auto Export' and 'Save'.

Every time the shader project is changed it will attempt to compile.  If the compile is successful and 'Auto Export' is checked it will copy all relevant files over to each of the selected Ultra projects in the 'Materials' folder.

If 'Auto Export" is disabled, you can go to File->Export All.

This is mine.

If you have the code above running in your application and your app is running as you edit your shader, you should see it update as you make changes.

[SpiderPig]

Updated to v1.1.  Release notes in download.

[SpiderPig]

Updated to v1.2.  Release notes in download.

[SpiderPig]

Updated to v1.3.  Macros now supported and an editor extension allows you to create a shader project from an existing material.