Cant start the 3D HDRP core template in 2021 LTS

Unity Engine
1

Like the title says. Anyone have any helpful tips on how to fix?
Getting this in the log:

Library\PackageCache\com.unity.shadergraph@12.1.6\Editor\Generation\Targets\BuiltIn\Editor\ShaderGUI\BaseShaderGUI.cs(212,34): error CS0103: The name ‘MaterialAccess’ does not exist in the current context

Library\PackageCache\com.unity.visualeffectgraph@12.1.6\Runtime\Utilities\Playables\VisualEffectActivation\VisualEffectActivationTrack.cs(14,31): error CS0246: The type or namespace name ‘VisualEffectActivationMixerBehaviour’ could not be found (are you missing a using directive or an assembly reference?)

2

I have a similar problem when going from 2020 LTS to 2021

Library\PackageCache\com.unity.visualeffectgraph@12.1.6\Runtime\Utilities\Playables\VisualEffectActivation\VisualEffectActivationTrack.cs(14,31): error CS0246: The type or namespace name ‘VisualEffectActivationMixerBehaviour’ could not be found (are you missing a using directive or an assembly reference?)

Library\PackageCache\com.unity.shadergraph@12.1.6\Editor\Generation\Targets\BuiltIn\Editor\ShaderGUI\MaterialAssemblyReference\RawRenderQueue.cs(12,24): error CS1061: ‘Material’ does not contain a definition for ‘rawRenderQueue’ and no accessible extension method ‘rawRenderQueue’ accepting a first argument of type ‘Material’ could be found (are you missing a using directive or an assembly reference?)

3

Hi,
I have solved this issue by:

  1. Deleted all unity-related files I could have found.
  2. Reinstalled unity.
  3. Reimported project - this step failed!!!
  4. Reimported project to NEW location (different drive) - imported correctly.
  5. Reimported project to former location and it did import correctly.

Fells like there is some residual unity data that conflicts and makes it impossible to update correctly.

4

I’m getting the same 2 errors (Unity 2022.1.21f1 with URP on a new project and on project upgrades)
I tried re-installing Unity with no luck.
What files do you have to delete?

5

I also join that club… on my mac all is fine, on my windows nop. The package cache of shadergraph and visualeffectgraph 13.1.8 are missing some meta files, some .cs files and assembly definitions.
Tried to wipe the whole unity package manager cache folder, project library folder, etc. I cant get it resolved.
When I copy the mac files in, it works until Unity detects “Changes” in the package cache and finally deletes them just to get the errors again :smile:

Also for me Unity 2021.3.21f1, I upgraded the project on the mac, put it into SCM, and now I have the mess here :smile:

6

Same here. I would not recommend installing 2022.1.21f without having a proper backup of your project. Waste half a day restoring my project to 2022.1.20f.

7

Same, shadergraph and visualleffectgraph broken in latest version

8

Same here

9

I too had this issue booting up 2022.1 yesterday to upgrade an older project when I was faced by this same error (URP though). I tried all the usual suspects like deleting package manager cache and re-installing editor after cleaning up all cache files under AppData - but the problem persists.

10

Same here. Come on Unity, test whether or not your product can upgrade existing projects rather than open one of the lacklustre starter projects.

Unity has a real dogfooding problem. Real shame they fired their entire game production team.

If you can’t handle Agile releases go back to Waterfall and start making Unity 6 or something.

11

I have similar problem upgrading to 2022.1.2.

I fixed the problem by deleting (.idea), (Library) and (Temp) files. Deleting Library alone didnt fix it before.

12

and you wonder since 2 week and this show-stopper problem is there, and no unity actions or replies to this at all.
Unity is becoming hell to deal with in last few years.

Please, kick this CEO, enough is enough. I don’t want to see a good application destroyed because of stupidity of management politics and greediness.

13

If you wanna do that you’ll have to purchase a majority share, idk about you, but I don’t have that kind of cash laying around.

14

I re-installed windows (clean install) for a separate issue so was curious to see if problem persisted. It still did. I also tried doing these steps (I had no .idea file though but a .vscode one so I removed that). But still exact same issue about shadergraph still persists. Seems no way of working on the project unless someone from has any other ideas.

Edit: Oh I can’t even create a new core template in URP either that’s a bummer

15

It’s a bug… they’ve added it as a release note… not exactly much of a warning… would have been better just to remove the build completely.
8565260--1146296--upload_2022-11-5_19-17-16.png

16

For me, it fails creating a brand new 3D (URP) project as well: no upgrade from 2022.1.20f1 necessary (even though I did discover the bug this way.)

It doesn’t seem to happen for me if the brand new project is legacy 3D (not URP.)

17

I just upgraded to 2022.1.23f1 and everything works fine both in my project and when creating an empty 2D URP projects.

PS.: The issue happens only on Windows, the same project on Mac worked totally fine.