0.51 InvalidOperationException: Cannot find Unity.NetCode metadata reference for assembly

Code (CSharp):

1. error Netcode: System.InvalidOperationException: Cannot find Unity.NetCode metadata reference for assembly BovineLabs.Saving
2.    at Unity.NetCode.Generators.TemplateParser.ParseTemplatesFromMetadata(GeneratorExecutionContext context, IList`1 templates)
3.    at Unity.NetCode.Generators.TemplateParser.ParseTemplates(GeneratorExecutionContext context)
4.    at Unity.NetCode.Generators.NetCodeSourceGenerator.Generate(GeneratorExecutionContext executionContext, Candidates candidates, IDiagnosticReporter diagnostic)
5.    at Unity.NetCode.Generators.NetCodeSourceGenerator.Execute(GeneratorExecutionContext executionContext)
6.  

I'm having an immediate issue after updating to 0.51 where if I have an assembly that does not use netcode is referenced by an assembly that does use netcode I just get the above locking error. It's fixable by making the assembly reference Netcode.

e.g.
GameAssembly
- References Netcode
- References Saving

SavingAssembly
- References nothing

Above error
Adding Netcode to SavingAssembly fixes error.
This happens in a brand new project just adding in in 2 existing libraries.

-edit- actually I think it might be reversed

Core references Netcode
Saving references Core

Even if saving does not use any Netcode it needs a reference on Netcode otherwise errors

 

Latest 2021.3.4f1 (latest)

Packages

Code (CSharp):

1.    "com.unity.burst": "1.7.2",
2.    "com.unity.entities": "0.51.0-preview.32",
3.    "com.unity.netcode": "0.51.0-preview.32",
4.    "com.unity.physics": "0.51.0-preview.32",
5.    "com.unity.rendering.hybrid": "0.51.0-preview.32",

I had it on 4-5 separate assemblies (of like 50) when upgrading - including 2 test assemblies.

 

Actually I got the error in a a brand new empty project copying in libraries in. When upgrading my project I was just getting a generic errors that didn't help at all and wouldn't compile (even though I deleted entire library before upgrading).

Luckily my project is extremely modular so instead I created a fresh project and slowly brought libraries into it until I got errors. Once I fixed these up and copied back changes to original project it compiled fine.

When I get off from work I'll try remove the references I added and see if it still fails.

I can probably rollback to my pre-upgrade state, test if I can repo the same thing in an empty project and if so just send you a library that fails.

 

Hi, have the same issue. can you also point me to your hotfix @CMarastoni ? thanks

 

Oh sorry I forgot about this as once solved it was no longer an issue.
I'll try find some time to see if my expected repo works.

 

I'm also getting the error with that kind of setup

AssemblyA references NetCode
AssemblyB references AssemblyA
-> this gives me "Cannot find Unity.NetCode metadata reference for assembly AssemblyB"

But as soon as AssemblyB also explictly references NetCode, the error goes away

 

After applying the hotfix, I'm getting this error:

First line says "Cannot load template .../GhostComponentSerializer.cs" and "Package com.unity.netcode not found", but GhostComponentSerializer.cs does exist at the specified path, and my custom netcode package is detected by the package manager

EDIT: actually, I get this same error even when I just copy the netcode folder into my Packages folder and remove netcode from my package manifest, without applying the hotfix. I might be doing something wrong?

I also haven't been able to repro in a new project, even when starting out in 2020.3 and then upgrating to 2021.3

 

@CMarastoni

I see, I've tried it again and now I can confirm the fix works. I was able to remove the NetCode reference from some of my assemblies and the errors don't appear anymore. Thanks!

I won't be able to use the hotfix for my project specifically, because it's an asset store project. But I'd be interested in knowing if there are plans to release an official package update containing the fix in the near future?

 

Hi @CMarastoni. I'm getting these messages with or without an assembly definition while following https://docs.unity3d.com/Packages/com.unity.netcode@1.0/manual/networked-cube.html as soon as I create the "Game.cs" script under the "Establishing a connection" section. The above steps don't seem to do anything (which isn't a surprise given there's no com.unity.netcode/Runtime/Gen folder in the latest version).

Anyway, any help would be appreciated.

 

Since there is no .../Runtime/Gen folder, I set it up this way:



On a hunch, I also tried deleting the existing "NetCodeSourceGenerator.dll" and renaming the Hotfix file "Unity.NetCode.SourceGenerators.dll" to match, but that didn't make a difference.

In both cases, Unity boots into safe mode and gives me variations on:
Packages\com.unity.netcode\Runtime\Physics\PhysicsVelocityVariant.cs(32,34): error CS0433: The type 'GhostPrefabType' exists in both 'GeneratorShared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' and 'Unity.NetCode, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'

 

Quick follow-up @CMarastoni - I created a new project and only installed Entities/Entity Graphics/Unity Physics/Netcode for Entities in that order. Restarted Editor. Then I created a new scene, a new C# script, named it as per the directions in the Getting Started -> Networked Cube page, copy/pasted the code and the assembly errors come right up.

 

Thanks again for your follow-up. I fear I may not have been clear.

I'm having this issue on Entities 1.0 latest, not on .51. I only posted here because it was the only thread I found mentioning the issue.

 

Sorry if that was confusing. Basically, I encountered the issue mentioned earlier in this thread (except I'm on 1.0) and tried out the proposed solution/hotfix directions you had previously given. However, the folder names didn't match so I just tried to guess where it would fit in the new folder structure (which is where that screenshot was taken from).

Regardless, the issue happens on a new project installing everything from package manager and not moving any folders/files around or trying to use the hotfix.

I hope this clarifies. Thank you for the follow up!