dfranx/shadered

★ 4,749C++Audience · developerComplexity · 3/5Setup · easy

Mindmap

mindmap
  root((SHADERed))
    What it does
      Live shader preview
      Pixel-level debugging
      Frame analysis
    Shader types
      Pixel shaders
      Compute shaders
      Geometry shaders
      Audio shaders
    Debugger features
      Breakpoints
      Variable inspection
      Performance heatmap
    Platforms
      Windows
      Linux
      Web version

mindmap root((SHADERed)) What it does Live shader preview Pixel-level debugging Frame analysis Shader types Pixel shaders Compute shaders Geometry shaders Audio shaders Debugger features Breakpoints Variable inspection Performance heatmap Platforms Windows Linux Web version

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Debug a broken pixel shader by clicking on a problem pixel and stepping through the shader code line by line to inspect variable values.

USE CASE 2

Write and preview GLSL visual effects like water reflections or particle animations without rebuilding a full game project.

USE CASE 3

Analyze shader performance with a frame heatmap to find which instructions run most often and are slowing down rendering.

USE CASE 4

Import a Shadertoy effect via the Shadertoy plugin and adapt it locally in SHADERed.

Tech stack

C++GLSLHLSLCMakeOpenGL

Getting it running

Difficulty · easy Time to first run · 30min

Prebuilt binaries are available for Windows and Linux, macOS requires building from source and is not officially supported.

In plain English

SHADERed is a desktop application for writing and debugging shaders. A shader is a small program that runs on a graphics card rather than the main processor, and it controls how pixels, geometry, or visual effects look on screen. Game developers and graphics programmers write shaders to create things like lighting, water reflections, or particle effects. SHADERed gives them a dedicated tool for writing and testing that code, with a live preview that updates as you type. The core feature is a shader debugger, which works similarly to how a debugger works for regular code. You pause the preview, click on a pixel you want to inspect, and then step through the shader code line by line to see what is happening. You can check the values of variables, set breakpoints that trigger only when a certain condition is met, and hover over expressions to see their current value. The frame analyzer goes a step further, letting you spot undefined behavior visually and see a heatmap of which instructions ran most often across the whole rendered frame. Beyond standard pixel shaders, SHADERed supports compute shaders and geometry shaders. It can import 3D models, textures, audio files, and cubemaps. There is support for render textures, instancing, and a multi-camera system. Audio shaders, which generate sound on the graphics card rather than consuming it as input, are also listed as a feature. An autocompletion system in the editor is designed specifically for shader code. The tool supports both GLSL and HLSL, the two most common shader languages, plus additional languages through a plugin system. Plugins are distributed through a dedicated store on the SHADERed website. Available plugins in the README include one for importing Shadertoy projects, one for capturing GIF animations, and one for writing shaders in the Rust language. Precompiled binaries are available for Windows and Linux, with Windows also supported via the Scoop package manager and Linux via Flatpak. A web version is accessible through the official website. Building from source requires CMake and a few graphics libraries. macOS can be built from source but is not officially supported.

Copy-paste prompts

Prompt 1

I'm writing a GLSL fragment shader and getting unexpected dark pixels. Using SHADERed, how do I set a conditional breakpoint that only triggers on pixels where a specific variable is below zero, then step through the code to inspect it?

Prompt 2

Show me how to import a 3D model and a cubemap texture into SHADERed to write an environment reflection shader in HLSL, with a live preview updating as I type.

Prompt 3

Using SHADERed's frame analyzer, how do I produce a heatmap of instruction frequency in my compute shader, and what should I look for to find the most expensive operations?

Open on GitHub → Explain another repo

← dfranx on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.