Search Issue Tracker
Fixed in 4.2.1
Votes
0
Found in [Package]
4.0.5
Issue ID
1204955
Regression
No
NullReferenceException errors are thrown when Instantiating a ProBuilderMesh in a build
Steps to reproduce:
1. Open user's attached project "RoyalCommanders.zip"
2. Build the scene "SoloTest" with developers build
3. Press the "Button" in the scene
4. Notice that Red cube was Instantiated after a short delay and error was thrown "NullReferenceException: Object reference not set to an instance of an object
at UnityEngine.ProBuilder.BuiltinMaterials.Init ()"
Expected results: The cube is Instantiated Instantly and nor errors are thrown
Actual results: The cube was Instantiated after a short delay and error was thrown
Reproducible with: 2019.2.16f1(4.0.5), 2019.3.0f4(4.1.2)
No Reproducible win: 2020.1.0a17(4.2.1)
Note: Versions lower than 2019.2 brakes making them unable to test. Not sure in which version exactly the bug was fixed
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 4.2.1):
The issue seems to be fixed in 2020.1.0a17(4.1.2)