#Major Project Breakage After Plastic SCM Rollback — URP & Asset References Corrupted

1 messages · Page 1 of 1 (latest)

winged carbon
#

Hey everyone,

I’m hoping someone here can help or at least shed some light on what’s gone wrong. I recently rolled my Unity project back to a previous version using Plastic SCM, and after doing so, a huge portion of my assets have broken — including all materials, scene visuals, and UI elements (Quantum Console, URP textures, etc.).

The console is showing:

Default Renderer is missing, make sure there is a Renderer assigned as the default on the current Universal RP asset: PC_RPAsset

I’ve since recreated the render pipeline settings and re-assigned them, which fixed the missing renderer error, but now almost all of my materials are desynced or have lost their shader/texture references entirely. It seems like Plastic didn’t properly restore or sync the .meta files, and Unity has lost the GUID links for a ton of assets.

I’ve tried the usual steps — deleting the Library folder, forcing a full reimport, ensuring visible meta files, and even rebuilding the pipeline asset — but the project is still in rough shape.

I understand this might not be Unity’s intended workflow issue, but I’ve got to admit — this experience with Plastic SCM has been incredibly frustrating. It feels like something as basic as rolling back a project should be safer, especially given how critical meta files are to Unity’s entire ecosystem.

Has anyone else run into this kind of rollback disaster before, and were you able to recover your materials and references without rebuilding them all from scratch? Any advice or workflows to prevent this kind of situation in the future would be massively appreciated.

Thanks in advance — and apologies if this comes off a bit ranty, I’m just trying to pick up the pieces here and understand what went wrong.

Thanks in Advance!

balmy elm
#

It sounds likely your version control setup is not properly configured. If meta files are not being committed, and project settings, those are oversights in what you've included in your version control repository

blissful hollow
#

yes: if your .meta files were not being tracked, then none of the references between assets were being recorded correctly