Search Issue Tracker
Won't Fix
Votes
1
Found in
5.4.0f3
Issue ID
966152
Regression
No
Directly serializing Matrix4X4 with JsonUtility yields different results than serializing a class with Matrix4X4 member
To reproduce:
1. Open the project, attached by the user (JsonSerializationBugTest.zip)
2. Open the "TestScene"
3. Enter Play mode
4. Observe the console
Expected: Matrix4X4 members are named the same regardless of whether the ToJson method serialized the Matrix4X4 directly or it serialized a class with a Matrix4X4 member
Actual: If Matrix4X4 is serialized directly, its members in the .json file will be named m00, m10, m20..., however, if a class is serialized which has a Matrix4X4 member, the matrix's member's names will be e00, e10, e20
Reproduced in 5.4.0f3, 5.5.5p1, 5.6.4p2, 2017.1.2p2, 2017.2.0p1, 2017.3.0b8, 2018.1.0a3
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
- Override move options in Inspector are not disabled when only one Override is added in URP Volume
- “NONE”/“ALL” text in Adaptive Probe Volumes Option Override is too light when Editor theme is set to Light
- Default Volume Profile property does not get reset when the property is selected and the reset button is pressed
- Saving Visual Effect Graph closes it in Visual Effect Graph window
- [Android] "Texture2D.ReadPixels" writes pixels into a texture incorrectly when used with OpenGLES3
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.