Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.21f1
2022.2.11f1
2023.1.0b8
2023.2.0a5
Issue ID
UUM-29388
Regression
Yes
System.Numerics.Vector4 returns incorrect values when the script is executed in the Player
Reproduction steps:
1. Open the attached project “VecTest”
2. Open “SampleScene” Scene
3. In the Console window menu press Editor and enable Player logging (you will be able to see script output this way)
4. Go to File > Build Settings and tick Development Build and Autoconnect Profiler options
5. Build and Run
6. Observe the Console
Expected result: Console outputs “In:<1, 2, 3, 4>:1 Out:<1, 2, 3, 4>”
Actual result: Console outputs “In:<1, 2, 3, 4>:1 Out:<-7.93019E-13, 8.856206E-43, -7.972745E+29, 8.82818E-43>”
Reproducible with: 2021.2.0a18, 2021.2.19f1, 2021.3.21f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a5
Not reproducible with: 2020.3.46f1, 2021.1.28f1, 2021.2.0a17
Reproducible on: Windows 10
Note: Doesn’t reproduce with IL2CPP or in Play mode
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
- NavMesh Surface is baked too high above the ground, making the NavMesh Agents hover above the ground when the HeightMesh is not built
- [Android] Crash on ProcessDynamicBatchGeometryJob with OpenGL or on DrawSharedGeometryJobs with Vulkan
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
Resolution Note:
This is a bug in the Mono JIT that we cannot easily correct. The System.Numerics code will work better with the CoreCLR runtime when that is shipped with Unity.