Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
Resolution Note (2023.2.X):
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.