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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note (fix version 4.2.1):
The issue seems to be fixed in 2020.1.0a17(4.1.2)