Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
11.0.0
Issue ID
1298167
Regression
No
[ShaderGraph] Error in the Console window does not point to the ShaderGraph with an error
Reproduction steps:
1. Open attached "case_1298167.zip"
2. In the Project window, open Test.shadergraph
3. Observe the error in the Console window
Expected result: The ShaderGraph name is printed in the error (or it is pointed by double-clicking)
Actual result: The ShaderGraph name is not printed
Reproducible with: 7.5.3 (2019.4.18f1), 10.3.1 (2020.2.3f1), 11.0.0 (2021.1.0b5, 2021.2.0a3)
Could not test with: 2018.4.31f1 (could not downgrade)
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
We made some efforts to reduce the noise produced by Shader Graph import errors. Additional debugging capabilities are really important and will be addressed in a future update, but this is feature-sized work for us. We're tracking the use case internally and will add it to our Public Roadmap as soon as we're ready to tackle it.