Search Issue Tracker
Fixed in 0.7.5-preview
Votes
0
Found in [Package]
0.5.3
Issue ID
1122461
Regression
No
[Addressables] A scripted object has a different serialization layout when loading (Read 184 bytes but expected 192 bytes)
How to reproduce:
1. Open the repro project ("Case-1122461.zip")
2. Open the Addressable tab
3. Select AAS Profile to local
4. Build player content
5. Build and run the project
6. The screen should stay white.
7. Open the log file at AppData\LocalLow\Goin' Places\VRame\output_log.txt
Expected results: no error messages regarding "different serialization layout" are found
Actual results: error messages regarding different serialization layout can be seen
Reproducible with: 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Reproducible with Package version 0.6.7
Could not reproduce with 2017.4, as it doesn't have Package Manager and Addressable package
Error message:
A scripted object (probably
UnityEngine.Rendering.PostProcessing.PostProcessLayer?) has a different
serialization layout when loading. (Read 184 bytes but expected 192 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any
of your scripts?
(Filename: Line: 2001)
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note (fix version 0.7.5-preview):
Fixed in 0.7.5-preview.