What causes an Unreal material Custom node HLSL compile error?

The Custom node's HLSL references inputs that are not declared as node input pins or omits a return statement, so the generated material function does not compile.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix an Unreal Material Custom Node HLSL Compile Error

Quick answer: Declare every variable you use as a named input pin on the Custom node, set the correct Output Type, and end the code with a return statement of that type.

Unreal's Custom material node wraps your HLSL in a generated function. Inputs become function parameters by pin name, and the node must return a value of the chosen output type. Mismatches break compilation. Here is how to fix it.

How to fix it

1. Declare inputs as pins

Every identifier your HLSL uses (like UV or Tex) must be added as a named input on the Custom node; the pin name becomes the variable name in the function.

2. Set the output type and return

Set the node's Output Type (e.g. CMOT Float3) and end with return value; matching that type; a missing return yields a compile error.

3. Read the shader compiler log

Enable r.ShaderDevelopmentMode 1 or check the Output Log for the exact HLSL line; the generated function shows your code with line offsets so you can map errors back.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unreal Engine error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.