Search Issue Tracker
By Design
Votes
0
Found in
2018.2.0b4
Issue ID
1041176
Regression
No
Unity.Mathematics.math.mul(float4x4 a, float4x4 b) arguments order is mismatched
How to reproduce:
1. Open given Unity project
2. Enter "SampleScene" scene
3. Enter Play Mode
4. Notice incorrect results in the console
5. Open "Float4x4Test" script and change function arguments (a, b) order to (b ,a) in line 17
6. Notice correct results in the console
Expected result: Output in the console should be http://www.wolframalpha.com/input/?i=%5B%5B1,2,3,4%5D,%5B5,6,7,8%5D,%5B9,10,11,12%5D,%5B13,14,15,16%5D%5D%5B%5B21,22,23,24%5D,%5B25,26,27,28%5D,%5B29,30,31,32%5D,%5B33,34,35,36%5D%5D
ab = 290 300 310 320
722 748 774 800
1154 1196 1238 1280
1586 1644 1702 1760
Actual result: Output in the console is:
a*b = 650 740 830 920
762 868 974 1080
874 996 1118 1240
986 1124 1262 1400
Reproducible with: 2018.3.0a1, 2018.2.0b4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animator State Labels are not Rendered correctly when using the Bitmap Renderer as the Default Editor Text Renderer
- LDR render target is used when HDR is enabled in URP and Recorder Source is set to 360 View
- Terrain Layer's changes are not added to the Undo history
- “IndexOutOfRangeException: Index was outside the bounds of the array.” error is thrown when large Text (TMP) GameObject Overflow field is set to Ellipsis
- The OnValidate method is not invoked when reverting changes on a Prefab Variant
Add comment