Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2021.2
2022.1
2022.1.0a15
Issue ID
1379872
Regression
No
[Serialization] UnityEngine.Hash128 fields overridden in prefabs generate poor property modification serialization
Reproduction steps:
1. Open the attached user's project "HashSerialization.zip"
2. Inspect the "SampleScene" with a Text Editor
Expected result:
- target: {fileID: 5907482044338101070, guid: 713a5b3f32873cb49a608e246c628f60, type: 3}
propertyPath: m_HashValue
value: 5a388598123920fbdff0f6dbab9818c7
objectReference: {fileID: 0}
Actual results:
- target: {fileID: 5907482044338101070, guid: 713a5b3f32873cb49a608e246c628f60, type: 3}
propertyPath: m_HashValue.bytes[15]
value: 199
objectReference: {fileID: 0}
Reproduces on: 2021.2.4f1, 2022.1.0a16
Could not test 2019.4.32f1 and 2020.3.23f1 due to errors not recognizing [SerializedProperty]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment