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.
Comments (1)
-
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
This is a duplicate of issue #1179418