stride-shader-asset-workflow

To fix stale Stride shader assets, enforce a forced asset rebuild sequence by running StrideCleanAsset followed by StrideCompileAsset before runtime debugging. This ensures generated shader keys and asset folders are synchronized with your current sdsl files.

The correct Stride shader workflow involves validating sdpkg asset folders, ensuring explicit linking or None items in csproj for deterministic behavior, and generating shader keys via StrideShaderKeyGenerator. This prevents build inconsistencies across standard templates and external shader folders.

StrideShaderKeyGenerator processes your sdsl shader files to produce generated key files, typically named *.sdsl.cs. These keys are required for deterministic shader behavior and must be included in your project's build workflow before debugging.

Yes, you need to configure explicit linking or None items in csproj for Stride shader assets. This ensures deterministic behavior during builds and prevents stale asset states when working with sdsl files across standard or shared shader folders.

Stride shader changes may not appear at runtime due to stale asset states. You need to verify sdpkg asset folder configuration, ensure StrideShaderKeyGenerator has produced updated keys, and force a rebuild using StrideCleanAsset and StrideCompileAsset before debugging.

Yes, this shader asset workflow supports projects managing Stride shader files in both standard templates and external or shared shader folders. It validates asset folders in sdpkg and enforces correct csproj linking regardless of the shader folder structure.