Search Issue Tracker
Duplicate
Votes
1
Found in [Package]
1.0.0
Issue ID
1171559
Regression
Yes
Unity UI package throws RaycastHit namespace errors when built-in Physics package is disabled
How to reproduce:
1. Create a new project
2. Open Package Manager and go to Built-in packages
3. Disable Physics built-in package
4. Observe the Console
Expected result: Unity UI package can operate without the Physics built-in package
Actual result: Uninstalling built-in Physics module results in errors thrown by the Unity UI package
Reproducible with: 2019.2.0b10 (Unity UI 1.0.0), 2019.3.0a3 (Unity UI 1.0.0)
Notes:
- Could not test with versions, earlier than 2019.2.0b1 and 2019.3.0a3 as Unity UI package was not present.
- Before Unity UI became a package instead of a built-in package, the problem was not reproducible.
- Disabling Physics built-in package require other built-in packages being disabled (XR, VR, Vehicles, Terrain Physics, Cloth), however disabling these packages does not have any effect on Unity UI package.
-
Resolution Note:
low priority for the moment, unlikely to be fixed for the immediate future.
-
mahrizh
Oct 15, 2019 05:09
Is there any workarounds like use mock classes for Physics and Physics2D? I have not found any.
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
- Size value in Particle System Curve's tab is highlighted with selection across all tab header
- Particle System Curve's Presets window has no visual indication of what preset is selected
- Blur shader doesn't work when the "Scene Color" Node is attached to the UI "Output" Node
- Particle System Curve presets can't be scrolled and some of them can't be selected if window is too narrow to fit them all
- Mistakes in multiple Particle System Components pop-up
This is a duplicate of issue #1179418