README.md

Platform	Build Status
Windows
MSYS2 (MinGW64)
Linux
macOS
Android
iOS
Emscripten
Coverage

Nazara Shading Language (NZSL)

NZSL is a shader language inspired by Rust and C++ which compiles to GLSL or SPIRV (without depending on SPIRV-Cross).

Why a new shader language?

I first designed NZSL for my game engine (hence the name) to help supporting Vulkan and OpenGL (ES) renderers with a unique shader language (without requiring #ifdef garbage).

I grew tired of the C-like syntax of both HLSL and GLSL, and though we can do a lot better and give it more features (like compile-time options, a modern import/module system instead of 40 year olds #include, etc.).

Some people got interested in the language to use in their own projects without requiring the game engine, so here it is!

What does it look like?

Simple example:

[nzsl_version("1.0")]
module TextureBlit;

import VertOut, VertexShader from Engine.FullscreenVertex;

external
{
    [binding(0)] texture: sampler2D[f32]
}

struct FragOut
{
    [location(0)] color: vec4[f32]
}

[entry(frag)]
fn main(input: VertOut) -> FragOut
{
    let texColor = texture.Sample(input.uv);

    let output: FragOut;
    output.color = texColor;

    return output;
}

How to use

NZSL is designed to be embedded in a game engine / game / graphics application that uses GLSL / SPIR-V for its shaders.

You can use it to generate GLSL, GLSL ES and SPIR-V in two non-exclusive ways:

1. Using the offline NZSL compiler (nzslc) ahead of time, in a way similar to glslangValidator or glslc today.
2. Use NZSL as a library in your application to compile shaders in a dynamic way, just as they're needed (which can be used to benefit from supported extensions to improve generation).

Offline compilation

Since there are no release yet, build the compiler using xmake which will handle all dependencies and build for you, simply run xmake in the project folder and you should have a standalone nzslc executable.

Example usage:

• Validating shader: nzslc file.nzsl
• Compile a shader to GLSL: nzsl --compile=glsl file.nzsl
• Compile a shader to SPIR-V: nzsl --compile=spv file.nzsl
• Compile a shader using modules to both GLSL and SPIR-V header includable version: nzsl --module module_file.nzsl --module module_folder/ --compile=glsl-header,spv-header file.nzsl

Run nzslc -h to see all supported options.

Use it as a library

You can easily integrate NZSL as a library in your project if you're using xmake as a build system (try it, it's amazing!) with:

-- nzsl is not yet on the official xmake-repo
add_repositories("nazara-repo https://github.com/NazaraEngine/xmake-repo")
add_requires("nzsl")

Simply add the nzsl package to your target and xmake will download/compile the latest version.

If you're using CMake, check out xrepo-cmake to integrate it.

Example usage:

#include <NZSL/Parser.hpp>
#include <NZSL/GlslWriter.hpp>
#include <NZSL/SpirvWriter.hpp>

int main()
{
    nzsl::Ast::ModulePtr shaderAst = nzsl::ParseFromFile("pbr.nzsl");

    nzsl::SpirvWriter spirvWriter;
    std::vector<std::uint32_t> spirv = spirvWriter.Generate(shaderAst);
    // spirv contains SPIR-V bytecode that can be directly given to Vulkan

    nzsl::GlslWriter glslWriter;
    nzsl::GlslWriter::Output output = glslWriter.Generate(shaderAst);
    // output.code contains GLSL that can directly be used by OpenGL
}

The library contains a lot of options to customize the generation process (target SPIR-V/GLSL version, GLSL ES, gl_Position.y flipping, gl_Position.z remapping to match Vulkan semantics, supported OpenGL extensions, etc.).

Commonly asked questions

Where can I find the language specification?

At this early point, there's no BNF notation or syntax document, but it's something I'd like to describe on the project wiki soon.

Why does it look so similar to WGSL?

The language syntax is mainly based on C++ and Rust, the resemblance with WGSL is accidental as I discovered it after the first working version of NZSL.

Why not just use SPIR-V and SPIRV-Cross?

SPIRV-Cross is interesting but it requires you to generate SPIR-V offline first, and thus use GLSL/HLSL which I grew out of love after a few years.

At my working place we're currently using huge HLSL-derived shaders with thousands of lines relying on #include and #pragma once, and it's very impractical and a pain to debug. The more translation layers you add, the more information you lose.

NZSL is designed to be small, fast and easy to debug, for example NZSL to GLSL retains a lot of the source code information which could be lost during SSA (SPIR-V) translation, even with debug symbols enabled.

Is there a DXIL/WGSL backend?

Not yet, as I don't target Direct3D or WebGPU yet.

DXIL is not very different from SPIR-V and WGSL looks a lot like NZSL so it should be quite easy to add, though.

See this issue for WGSL.

Are there limitations?

Unfortunately yes, NZSL is in its early stage and is currently only capable of regular operations in compute, fragment and vertex stages, not all intrinsics are supported, bit operators are not yet supported (see #8) and more.

The reason isn't that it's complicated to add, but that I didn't need it yet. Most feature can be added quite fast so do not hesitate to open an issue and/or check the roadmap.

I don't like the syntax

That's unfortunate, however I'm open to suggestions to improve NZSL syntax, even for breaking changes (one feature of NZSL modules is to allow breaking changes without breaking all shaders), so do not hesitate to open an issue.

I want to contribute

Welcome aboard! Do not hesitate to check the issues for "good first issues" which should be quite easy to do.

You can also check the roadmap.

Simply fork the project, make some changes and open a pull request once you're ready to merge your work!