Search Issue Tracker
Fixed in 1.11.2
Votes
0
Found in [Package]
1.11.2
Issue ID
1256876
Regression
Yes
NullReferenceException is thrown when using Addressables.InstantiateAsync to instantiate a Prefab with complex Mesh Collider
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
3. Exit the Play Mode
4. Enter the Play Mode again
5. Observe the Console Window
Expected result: No errors are thrown
Actual result: NullReferenceException error is thrown
Reproducible with: 2019.3.2f1, 2019.4.3f1, 2020.1.0a20 (1.11.2)
Not reproducible with: 2018.4.24f1, 2019.3.1f1, 2020.1.0a21, 2020.1.0b14, 2020.2.0a17 (1.11.2)
Couldn't test with: 2019.3.08, 2019.3.0f3 ("Reached the maximum polygons limit" error is thrown)
Workaround: Downgrading to Unity 2018.4.24f1 and upgrading the project back to the initial version (also need to fix references to Materials and Meshes after)
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 1.11.2):
Fixed in Unity 2020.1.0a21 and above