Search Issue Tracker
Fixed in 10.0.0
Votes
0
Found in [Package]
9.0.0 - preview.14
Issue ID
1241826
Regression
No
[ShaderGraph] Shader Graph scripts use a dangling namespace 'Data.Util'
How to reproduce:
1. Create a new Unity project
2. Download and import the Shader Graph package
3. Search for and inspect one of the scripts containing the Data.Util namespace(e.g. 'ActiveFields.cs')
Expected result: the scripts are not using a dangling namespace (instead using something like 'UnityEngine.Data.Util')
Actual result: the scripts are using a dangling namespace 'Data.Util'
Reproducible with: 2019.3.13f1, 2020.1.0b8, 2020.2.0a11
Could not test with: 2017.4.40f1(package unavailable), 2018.4.22f1(Data.Util namespace does not exist at all)
Reproducible with package versions: 7.3.1, 9.0.0 - preview.14
Could not test with: 6.9.2(Data.Util namespace does not exist)
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
- Switching a Type QueryBlock to prefabs fails
- Search Index Manager allows deleting Empty Index List when clicking on “-“ button, throwing “ArgumentOutOfRangeException” error in the Console window
- "System.ArgumentOutOfRangeException" error is thrown when baking Adaptive Probe Volumes
- Project Directory is opened when Opening the Editor Log from the Console Window and the Editor is launched with the -nolog argument
- "vector<bool> too long" error is thrown when using UnityYAMLMerge
Resolution Note (fix version 10.0.0):
This can be fixed in the next major version bump of the package. Unfortunately due to semantic versioning, we cannot edit the namespace for minor or patch versions and therefore the problem will need to be worked around on the user end for the 7.x package versions.