Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.3f1
Issue ID
1049287
Regression
No
Generic class values are not deserialized on built game
Steps to reproduce:
1. Open user attached project
2. Play the scene
3. Notice that the speed is set to 9
4. Build and run
5. Speed value is now invalid
- output_log throws: A script behaviour (probably Shell.FloatVariable?) has a different serialization layout when loading. (Read 44 bytes but expected 100 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?
Expected result: speed value should stay 9 on built game
Tested on: Windows, Android
Reproduced in: 2018.3.0a2, 2018.2.0b8, 2018.1.4f1, 2017.4.5f1, 2017.3.2f1 2017.2.3p1
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
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
- GPU usage doubles when a project is running in the background
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.