Search Issue Tracker

Fixed in 10.x

Fixed in 7.1.6, 8.2.0

Votes

0

Found in [Package]

8.1.0

Issue ID

1212179

Regression

No

Compute Shader compilation error is thrown after building a new HDRP project - wait new template

Package: SRP HD Template

-

How to reproduce:
1. Create a new project with HDRP template
2. Attempt to build the project
3. Open the Console window

Expected result: No Console errors are thrown, Scene and Game views are rendered correctly
Actual result: Compute Shader compilation error is thrown, Scene and Game views are not rendered

Reproducible with: 2020.2.0a17, 2020.1.0b14, 2020.1.0a20 (8.1.0)
Not reproducible with: 2020.1.0a17, not reproducible with 2019.3 or 2019.4 and HDRP 7.x.x.

Error:
Exception: Compute Shader compilation error on platform D3D in file DepthOfFieldKernel.compute:2: failed to open source file: 'DepthOfFieldCommon.hlsl' at kernel KParametricBlurKernel
HDRP will not run until the error is fixed.

UnityEngine.Rendering.HighDefinition.HDRenderPipeline.ValidateResources () (at Library/PackageCache/com.unity.render-pipelines.high-definition@7.1.7/Runtime/RenderPipeline/HDRenderPipeline.cs:516)
UnityEngine.Rendering.HighDefinition.HDRenderPipeline..ctor (UnityEngine.Rendering.HighDefinition.HDRenderPipelineAsset asset, UnityEngine.Rendering.HighDefinition.HDRenderPipelineAsset defaultAsset) (at Library/PackageCache/com.unity.render-pipelines.high-definition@7.1.7/Runtime/RenderPipeline/HDRenderPipeline.cs:334)
UnityEngine.Rendering.HighDefinition.HDRenderPipelineAsset.CreatePipeline () (at Library/PackageCache/com.unity.render-pipelines.high-definition@7.1.7/Runtime/RenderPipeline/HDRenderPipelineAsset.cs:27)
UnityEngine.Rendering.RenderPipelineAsset.InternalCreatePipeline () (at <fb2fc6957fb545e2b617c8816705aa34>:0)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

  1. Response avatar

    Resolution Note (fix version 10.x):

    The embeded template files that ship with the editor installation need to be updated (because it is currently trying to upgrade HDRP and first importing the project at the same time).

    Latest version of Unity shouldn't have the issue anymore.

    As a workaround, clearing the Library folder and reimporting the project fixes the issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.