Search Issue Tracker
Fixed in 4.0.5
Votes
0
Found in [Package]
4.0.4
Issue ID
1151384
Regression
Yes
Probuilder compilation fails on 2018.4 because it uses UnityEngine.UIElements instead of UnityEngine.Experimental.UIElements
Steps to reproduce:
1. Create a new project in Unity 2018.4
2. Import Probuilder package
Expected results: No compilation errors
Actual results: Multiple compilation errors caused by the package attempting to use UnityEngine.UIElements library instead of UnityEngine.Experimental.UIElements
Reproducible on: 2018.4.0f1 (b6ffa8986c8d)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment