Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.0.0-pre.5
Issue ID
NCCBUG-111
Regression
No
Namespace 'umul128' error when Multiplayer Netcode for GameObjects is installed along with Common.Logging.Core library
How to reproduce:
1. Open the attached project from "Unity3dSimpleSampleNet461-master.zip"
2. Observe Console for the error "The type or namespace name 'umul128' does not exist in the namespace 'Common'"
Expected result: No namespace errors
Actual result: Conflicting namespaces introduces errors
Reproducible with: 1.0.0-pre.2, 1.0.0-pre.5 (2020.3.28f1, 2021.2.11f1, 2022.1.0b7, 2022.2.0a4)
Not reproducible with: 2019.4 (Package not supported)
Note:
1. Workaround for this error is to replace all Common references in the Collections package with Unity.Burst.Intrinsics.Common
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
There are no fixes planned for this Bug