Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a1
Issue ID
1046685
Regression
Yes
UI module is not detected when upgrading the project from 2018.2 to 2018.3
UI module is not detected when upgrading the project from 2018.2 to 2018.3
Steps to Reproduce:
1. Create a project in 2018.2 using UI components
2. Upgrade the project to 2018.3
3. Open the Scene and Play
Actual Result:
1. UI Items are not rendered
2. Right Click on Heirarchy Window, "UI" Menu Option is missing.
Works with : 2018.2.0b7, 2018.1.0f2
Reproduces on: 2018.3.0a1
Environment:
Windows 10
Stack Trace :
MissingComponentException: There is no 'CanvasRenderer' attached to the "PlatformInfo" game object, but a script is trying to access it.
You probably need to add a CanvasRenderer to the game object "PlatformInfo". Or your script needs to check if the component is attached before using it.
UnityEngine.UI.Graphic.Rebuild (CanvasUpdate update) (at C:/buildslave/unity/build/Extensions/guisystem/UnityEngine.UI/UI/Core/Graphic.cs:526)
UnityEngine.UI.CanvasUpdateRegistry.PerformUpdate () (at C:/buildslave/unity/build/Extensions/guisystem/UnityEngine.UI/UI/Core/CanvasUpdateRegistry.cs:198)
UnityEngine.Canvas:SendWillRenderCanvases()
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment