Fix: Unity Shader Graph Custom Function Not Compiling

Here is how to fix Unity Shader Graph Custom Function not compiling. You create a Custom Function node, point it to your .hlsl file, set the function name, add inputs and outputs. The node shows a red error bar — just “Shader Error.” Custom Function is powerful but strict about naming conventions that the UI does not explain.

The Symptom

Custom Function node shows a compile error in Shader Graph. Material preview is pink. Other standard nodes compile fine.

What Causes This

Function signature mismatch. Shader Graph generates a call with specific parameter names based on your node’s input/output definitions. If the HLSL function has different parameter names, the generated call does not match.

Missing precision suffix. Custom Functions must use precision-suffixed naming: MyFunction_float or MyFunction_half. Shader Graph calls the variant matching the graph’s precision.

File not found. The Source field must point to a .hlsl file inside Assets/ or Packages/. Files in Editor/ folders do not resolve.

Output parameter not out. HLSL output parameters must use the out keyword.

The Fix

Step 1: Match function signature exactly. If your node has inputs A (float) and B (float3) and output Result (float3):

void MyCustom_float(float A, float3 B, out float3 Result)
{
    Result = B * A;
}

Function name = node’s Function field + “_float”. Input names match node inputs. Output names match node outputs. All case-sensitive.

Step 2: Provide both precision variants.

void MyCustom_float(float A, float3 B, out float3 Result) { Result = B * A; }
void MyCustom_half(half A, half3 B, out half3 Result) { Result = B * A; }

If the graph switches to half precision (mobile), it calls _half. Missing it causes compile failure on mobile builds.

Step 3: Use String mode for simple functions. Instead of a file, select Type = String and write the body inline: Result = A * B; String mode wraps your code in the correct function signature automatically.

Step 4: Verify file path. The Source field should show the .hlsl file as a Unity asset reference. If it shows “None,” the file is not recognized. Ensure file extension is .hlsl and it is inside Assets/.

Debugging

Select the material. In the Inspector, click “Edit Shader” or view the generated shader code. Search for your function name. The compiler error lines tell you exactly which parameter is wrong.

Understanding the issue

Shader bugs manifest visually but trace to invisible state. Triage requires understanding the runtime context as much as the source.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Custom Function is string-exact. Function name, parameter names, precision suffix — all must match the node definition character for character.”

Related Issues

For pink materials, see Unity Pink or Magenta Materials. For preview issues, Shader Graph Preview Black Screen.

FunctionName_float with matching params. Both precision variants. File in Assets/.