Search Issue Tracker
Fixed
Votes
0
Found in [Package]
7.2.1
Issue ID
1228498
Regression
No
error CS0234: The type or namespace name 'ShaderGraph' does not exist in the namespace
How to reproduce:
1. Clear out your C:\Users\[username]\AppData\Local\Unity\cache\packages folder
2. Unzip the attached packages.unity.com.zip file into C:\Users\[username]\AppData\Local\Unity\cache\packages (should be cache\packages\packages.unity.com\...)
3. Open attached project "pactest.zip"
4. Observe the Console window
Expected result: no errors are thrown
Actual result: "Library\PackageCache\com.unity.visualeffectgraph@7.2.1\Editor\ShaderGraph\VFXShaderGraphParticleOutput.cs(6,19): error CS0234: The type or namespace name 'ShaderGraph' does not exist in the namespace 'UnityEditor' (are you missing an assembly reference?)" is thrown
Reproducible with: 2018.4.19f1, 2019.3.6f1, 2020.1.0b3, 2020.2.0a4
Could not test with: 2017.4 (Shader Graph was not yet released)
Comments (3)
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
- NullReferenceException is thrown when assigning an Object to a custom DebugUI.ObjectField in Rendering Debugger
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
mr_noodler
Oct 08, 2024 01:11
Where are the attachment files that I am supposed to run?
UnrealSoftware
Jun 18, 2023 10:19
I had the same issue after upgrading to Unity 2022.3.2f1 and trying to add URP via package manager to an existing project.
Was able to fix it by removing the C:\Users\[username]\AppData\Local\Unity\cache\packages folder.
Jason-King
Jan 27, 2022 04:08
I had this issue when I moved the source out of the Plugins folder into a separate folder - and only could be resolved by moving the code back into the Plugins folder.