Migration of old project to Unity 6 fails for Rendering.Universal package

Unity Engine
, , ,
1

I have an issue with migration of an old project to Unity 6.
The old project was made with Unity 2020.2.0.a18, where Rendering package was still Experimental. Now I have Unity 6000.0.22f1, (it comes with Visual Studio 17.11.5).
I loaded the old project to new Unity and it works, except every script reference to Rendering.Universal is faulty.
From what I hear, all I have to do is to change this:
using UnityEngine.Experimental.Rendering.Universal;

to this:
using UnityEngine.Rendering.Universal;

but referencing things like Light2D still cause errors (cannot find name or namespace)

What am I missing to complete the migration? Regenerating project files did not help.

2

Apparently, Rendering.Universal works for new projects.
That means migrating old projects to new Unity leaves some trash behind, which makes the compiler not recognize the new packages. What could this trash be?

Alternatively, the old projects did not have some setting, that the new projects have.

3

It seems some classes are missing from the namespace in my project, but I don’t understand why.

I have Universal RP version 17.0.3, and Light2D is not there. There is stuff like LightExtensions, LightLayerEnum…
Any idea why is that?

4

Hi @glock18_unity! I was facing this error too. If you are using Assembly Definitions, make sure to reference the new Unity.RenderPipelines.Universal.2D.Runtime Assembly Definition, it will include Light2D.