Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.4.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.2f1
2019.1.0a1
2019.2.0a1
Issue ID
1118631
Regression
No
System.Numerics Vector sizes are all 16 bytes instead of 8, 12 and 16 bytes
How to reproduce:
1. Open the attached "UnityBugSystemNumericsVector2Size.zip" project
2. Open the "Bug" scene
3. Enter Play mode
Expected results: Console prints out the correct values for the sizes of System.Numerics.Vector2 and System.Numerics.Vector3(8 and 12)
Actual results: Console prints out 16 twice
Reproducible with: 2017.4.18f1, 2018.3.3f1, 2019.1.0a14, 2019.2.0a2
---------------------------------------------------------------------------------------
Fixed in: 2019.1.0b5, 2019.2.0a5
Comments (1)
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
dfields-msft
Sep 12, 2019 00:08
I'm hitting this as well, and it's causing problems for some code that's trying to interop with a native plugin. The plugin properly fills a System.Numerics.Vector3[] buffer using a stride of 12 bytes, but the script code running in 2018.4.6 accesses it with a stride of 16 bytes, which obviously doesn't work as intended. When can this be patched in 2018.4?
PS- We've been discussing this over on an unrelated GitHub issue here:
https://github.com/microsoft/MixedRealityToolkit-Unity/issues/3939#issuecomment-530611503