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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
There are no fixes planned for this Bug