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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note (fix version 0.7.5-preview):
Fixed in 0.7.5-preview.