Search Issue Tracker
Fixed in f7196971fa955d71839d5f18496351e3ad48a7c9
Votes
0
Found in [Package]
2020.2.0a11.1312
Issue ID
1304146
Regression
No
[Shadergraph] Virtual Texture "Layer Reference" name doesn't sanitize pasted inputs
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: the pasted string is sanitized
Actual result: the pasted string makes it in with invalid characters, the graph breaks, and although errors show up in the graph, no errors show up in console, making the problem difficult to debug (this is why I chose severity 2)
On top of fixing the bug, it should be looked into why no errors were printed to console, which in and of itself is a bug. Whatever caused that should also be fixed.
Related doc ticket: https://unity3d.atlassian.net/browse/DOC-2827
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version f7196971fa955d71839d5f18496351e3ad48a7c9):
Layer reference name is now sanitized using our hlsl sanitizing rules. Also fixed name collisions checking the display name instead of the reference name.