stride-shader-asset-workflow

Stride SDSL shaders fail after moving because generated shader key files and sdpkg asset folder references become stale. Updating csproj shader metadata and regenerating shader key classes resolves the broken asset pipeline registration.

To add a new shader in Stride, connect the SDSL file through the sdpkg asset folder and csproj configuration, then execute an ordered asset rebuild workflow: update generated files, clean assets, compile assets, and validate changes before runtime testing.

Generated shader key classes in Stride are C# code artifacts that bind SDSL shader parameters to the asset pipeline. You must regenerate them whenever adding, moving, renaming, or debugging shader files to ensure reliable parameter bindings.

Yes, this Stride shader asset workflow applies specifically to Stride C# dotnet projects. It fixes incorrect asset registration and stale generated files by requiring correct sdpkg asset folders, csproj shader metadata, and explicit asset rebuild targets.

Fix Stride shader runtime issues by applying an explicit asset rebuild workflow: update generated shader key files, clean stale assets, compile assets through the pipeline, and validate the SDSL integration before testing the game engine.