Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3
2020.1
Issue ID
1187967
Regression
No
[SerializeReference] looses object reference to Material in build
Reproduction steps:
1. Open the attached project "SerializeReference" and scene "MaterialList"
2. In the Hierarchy, select "MaterialList" and make sure "Test1", "Test2" materials are attached to the "Materialcells" list
3. Enter Play Mode and see both Materials being logged in the Console
4. Build and Run the project.
5. Open Player Log by clicking the three dots in the right corner of the Console window and selecting "Open Player Log"
Expected result: Both Materials are being logged in the Player Log
Actual result: Materials are null
Reproducible with: 2019.3.0a2, 2019.3.0b6, 2020.1.0a8
Could not test with: 2017.4.33f1, 2018.4.11f1, 2019.2.8f1, 2019.3.0a1 (SerializeReference inaccessible due to its protection level)
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Resolution Note (fix version 2020.1):
Fixed in 2019.3.0f1, 2020.1.0a15