Unity-Technologies / multiplayer-community-contributions

Community contributions to Unity Multiplayer Networking products and services.
MIT License
421 stars 161 forks source link

Lots of error after import com.community.netcode.extensions #171

Open tortoise00q opened 2 years ago

tortoise00q commented 2 years ago

I open an empty unity project and impot com.community.netcode.extensions by the git link (https://github.com/Unity-Technologies/multiplayer-community-contributions.git?path=/com.community.netcode.extensions) and I just rechieved lots of error about namespace not exist or no suitable method found to override.

Unity version: 2021.2.13f1 Netcode for GameObjects Community Extensions Package 1.0.1 Capture

akoolenbourke commented 2 years ago

There's also a GUID conflict in the Unity Transports GUID [6960e84d07fb87f47956e7a81d71c4e6] for asset 'Packages/com.unity.netcode.adapter.utp/Runtime/UnityTransport.cs' conflicts with: 'Packages/com.unity.netcode.gameobjects/Runtime/Transports/UTP/UnityTransport.cs' (current owner) We can't assign a new GUID because the asset is in an immutable folder. The asset will be ignored.

dribeirofernandes commented 2 years ago

This is happening to me as well, any updates on how to fix this? @LukeStampfli

WhippetsAintDogs commented 2 years ago

178

CodeSmile-0000011110110111 commented 1 year ago

I have the same issues, with these UNET errors remaining after clearing console:

Library\PackageCache\com.community.netcode.extensions@9a480a5863\Runtime\NetworkDiscovery\ExampleNetworkDiscoveryHud.cs(4,32): error CS0234: The type or namespace name 'UNET' does not exist in the namespace 'Unity.Netcode.Transports' (are you missing an assembly reference?)

Library\PackageCache\com.community.netcode.extensions@9a480a5863\Runtime\NetworkManagerHud\NetworkManagerHud.cs(4,32): error CS0234: The type or namespace name 'UNET' does not exist in the namespace 'Unity.Netcode.Transports' (are you missing an assembly reference?)
akoolenbourke commented 1 year ago

I tried updating from latest code today and still there's a transport conflict with UnityTransport.cs. Someone else must be seeing this right?

Should this extension even be using the adapter.utp, or does the Unity Transport for NGO already handle all this anyway?

I made the package embedded, removed the dependency on xxxx.adapter.utp and things seemed to work. then when I went to actually try and use NetworkDiscovery, after a StartClient and then ClientBroadcast the server gives me this.

Invalid allocation label passed to UnsafeUtility::Free UnityEngine.StackTraceUtility:ExtractStackTrace () Unity.Netcode.FastBufferWriter:Dispose () (at Library/PackageCache/com.unity.netcode.gameobjects@1.0.0/Runtime/Serialization/FastBufferWriter.cs:125) NetworkDiscovery`2/d__27<DiscoveryBroadcastData, DiscoveryResponseData>:MoveNext () (at Packages/com.community.netcode.extensions/Runtime/NetworkDiscovery/NetworkDiscovery.cs:224) UnityEngine.UnitySynchronizationContext:ExecuteTasks ()

Is this package actually maintained and tested with any 1/2 recent version of NGO?

paatz04 commented 1 year ago

I tried updating from latest code today and still there's a transport conflict with UnityTransport.cs. Someone else must be seeing this right?

Should this extension even be using the adapter.utp, or does the Unity Transport for NGO already handle all this anyway?

I made the package embedded, removed the dependency on xxxx.adapter.utp and things seemed to work. then when I went to actually try and use NetworkDiscovery, after a StartClient and then ClientBroadcast the server gives me this.

Invalid allocation label passed to UnsafeUtility::Free UnityEngine.StackTraceUtility:ExtractStackTrace () Unity.Netcode.FastBufferWriter:Dispose () (at Library/PackageCache/com.unity.netcode.gameobjects@1.0.0/Runtime/Serialization/FastBufferWriter.cs:125) NetworkDiscovery`2/d__27<DiscoveryBroadcastData, DiscoveryResponseData>:MoveNext () (at Packages/com.community.netcode.extensions/Runtime/NetworkDiscovery/NetworkDiscovery.cs:224) UnityEngine.UnitySynchronizationContext:ExecuteTasks ()

Is this package actually maintained and tested with any 1/2 recent version of NGO?

I'm getting the same error on the server when running the ClientBroadcast. Any solutions to this?