Search Issue Tracker
Fixed in 7.0.2
Fixed in 7.1.1
Votes
4
Found in [Package]
2019.3.0a12
Issue ID
1174981
Regression
Yes
[Universal RP] Template project throws Exception: Cannot load... .../Autodesk Interactive.shadergraph Null returned
[Universal RP] Creating template project throws Exception: Cannot load... ...Autodesk Interactive.shadergraph Null returned.
When creating a new project, if the user selects the Universal RP template, upon loading the created project they will note the following exception produced 123 times:
Exception: Cannot load. Incorrect path: Packages/com.unity.render-pipelines.universal/Shaders/Autodesk Interactive/Autodesk Interactive.shadergraph Null returned.
UnityEngine.Rendering.ResourceReloader.Load (System.String path, System.Type type, System.Boolean builtin) (at /home/builduser/buildslave/unity/build/build/libcache/Library/PackageCache/com.unity.render-pipelines.core@7.0.1/Runtime/Utilities/ResourceReloader.cs:153)
UnityEngine.Rendering.ResourceReloader.SetAndLoadIfNull (System.Object container, System.Reflection.FieldInfo info, System.String path, System.Boolean builtin) (at /home/builduser/buildslave/unity/build/build/libcache/Library/PackageCache/com.unity.render-pipelines.core@7.0.1/Runtime/Utilities/ResourceReloader.cs:162)
UnityEngine.Rendering.ResourceReloader.ReloadAllNullIn (System.Object container, System.String basePath) (at /home/builduser/buildslave/unity/build/build/libcache/Library/PackageCache/com.unity.render-pipelines.core@7.0.1/Runtime/Utilities/ResourceReloader.cs:45)
UnityEngine.Rendering.ResourceReloader.ReloadAllNullIn (System.Object container, System.String basePath) (at /home/builduser/buildslave/unity/build/build/libcache/Library/PackageCache/com.unity.render-pipelines.core@7.0.1/Runtime/Utilities/ResourceReloader.cs:36)
UnityEngine.Rendering.Universal.UniversalRenderPipelineAsset.LoadResourceFile[T] () (at /home/builduser/buildslave/unity/build/build/libcache/Library/PackageCache/com.unity.render-pipelines.universal@7.0.1/Runtime/Data/UniversalRenderPipelineAsset.cs:219)
UnityEngine.Rendering.Universal.UniversalRenderPipelineAsset.get_editorResources () (at /home/builduser/buildslave/unity/build/build/libcache/Library/PackageCache/com.unity.render-pipelines.universal@7.0.1/Runtime/Data/UniversalRenderPipelineAsset.cs:229)
UnityEngine.Rendering.Universal.UniversalRenderPipelineAsset.GetMaterial (UnityEngine.Rendering.Universal.DefaultMaterialType materialType) (at /home/builduser/buildslave/unity/build/build/libcache/Library/PackageCache/com.unity.render-pipelines.universal@7.0.1/Runtime/Data/UniversalRenderPipelineAsset.cs:269)
UnityEngine.Rendering.Universal.UniversalRenderPipelineAsset.get_defaultMaterial () (at /home/builduser/buildslave/unity/build/build/libcache/Library/PackageCache/com.unity.render-pipelines.universal@7.0.1/Runtime/Data/UniversalRenderPipelineAsset.cs:465)
UnityEditor.Rendering.Universal.MaterialReimporter:ReimportAllMaterials()
Steps to reproduce
- With Unity 2019.3.0a12(+), create/open a new project using the Universal RP template
- When the project is opened, observe the mentioned errors produced in the console
-
ahumanbeing
Sep 01, 2019 15:20
I found that this is a shader error for my ui elements. After upgrading to universal pipeline, I had to manually change all default ui shaders to universal pipeline > ui > then choose from there. This also solves the long load time lag when playing a scene in the latest Unity beta. Hope this helps.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader error db grows on each build
- Android ARCore build fails with 2019.4 due to outdated Gradle
- [tvOS] Visual artifacts are present when Ambient Occlusion is enabled and Dynamic Resolution is reduced
- Texture Importer Inspector throws errors when a built-in texture inspector is overwritten in C#
- Invalid AABB error is thrown when moving a Particle with Velocity over Lifetime and Limit Velocity over Lifetime modules
Resolution Note (fix version 7.0.2):
Could not reproduce in 2019.3.0b8, closing as fixed.