Search Issue Tracker
Fixed in 4.3.2
Votes
0
Found in [Package]
4.3.1
Issue ID
1258589
Regression
Yes
[Probuilder] Sample Runtime example throws errors on importing
Sample Runtime example in Probuilder throws casting errors from Mesh to GameObject on importing. Refer the attached video
Steps to reproduce
1) Create a new project
2)Window > Package Manager > Install Probuilder
3) Import Runtime sample
Actual result: Errors are thrown on importing runtime sample
Expected result: No errors should be thrown on importing the runtime sample
Reproducible on:
2020.1.0b14 and 2020.2.0a16 with Probuilder package version 4.3.1
Working fine on:
2020.1.0b14 and 2020.2.0a16 with Probuilder package version 4.2.3
Environment:
Windows 10 and Mac 10.15
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Resolution Note (fix version 4.3.2):
https://github.com/Unity-Technologies/com.unity.probuilder/pull/308