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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
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.