Search Issue Tracker
Fixed in 4b29153fc88df46ca61152c273d232701075a598
Votes
0
Found in [Package]
2020.2.0a11.1312
Issue ID
1304162
Regression
No
[Shadergraph] Action that causes the graph to error does not print errors to console
Repro steps:
1. Create a shadergraph
2. Create a virtual texture
3. Copy and paste a word with an invalid symbol (such as an exclamation point or a space) into the "Layer Reference" space in the virtual texture options in the node settings in the graph inspector
Expected result: if the bug still reproduces, an error should be printed to the console with a stack trace or line number so the user can more easily figure out what's going on
Actual result: there are errors in the graph but the errors are not printed to the console
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note (fix version 4b29153fc88df46ca61152c273d232701075a598):
Added a catch-all console error on save (import) for shaders