Importer(DefaultImporter) generated inconsistent result for asset

Seems that the newly introduced shader caching scheme produces some inconsistent shader binaries.
Every time I edited my compute shader in Visual Studio, the shader code has chance to get messed up in the engine. Is there anyone experienced this before? Or this is a bug in newest version?

I'm also getting this (since 2020.2.1f1)...

2020.2.1f1 is kinda crap, cant even publish to cloud half the time..

I get a lot of these for all sorts of assets.

I sometimes even get them for FOLDERS (and nothing else), ffs.

6702373--769552--upload_2021-1-8_11-56-48.png

Back with a vengeance in 2021.1.1 :P

Oh, Unity...

1 Like

Just upgrated to 2020.2.5 and I 'm still getting warnings like this from time to time. Appart from thw warning which makes me kinda worry, everything seems to work though.

Still not fixed in 2020.3

6925961--812741--upload_2021-3-11_22-10-44.png

It temporarily goes away by deleting the library, but I can't keep deleting the library more often than my current once a week.

Can confirm that this bug is indeed not fixed.

I had been noticing it in my 2020.2 sandbox project to varying degrees of duplicity. This morning, I upgraded to 2020.3.0f1 after reading in the patch notes that it had been fixed...

Nope, still here.
6932194--814022--2020.3.0f1-console-01.png

Unity 2021.1: This is happened for scene asset

Come on Unity, this issue is still gong strong in 2021.1.2. We see these every day all the day...

Are we really gonna have to buy one of those Console replacement assets just to filter these warnings out?

Boom! Finally fixed in 2021.1.5 but you have to do an "Assets->Reimport All" to get rid of them!
Spotted it in the release notes

6 Likes