Search Issue Tracker
Fixed in 1.0.X
Fixed in 1
Votes
8
Found in [Package]
2019.2.0a8
2019.2.2f1
2019.3.0a3
2020.1.0a1
Issue ID
1179418
Regression
Yes
Namespace errors are thrown when Physics 2D Built-in package is removed
How to reproduce:
1. Create a new project
2. Open Package Manager window (Window->Package Manager)
3. In Package Manager, top middle menu select Built-in packages
4. Disable Tilemap package
5. Disable Physics 2D
Expected result: No error is thrown
Actual result: Namespace error is thrown
Reproducible with: 2019.2.3f1, 2019.3.0b1, 2020.1.0a2
Not reproducible with: 2017.4.32f1 (Package Manager was not present), 2018.4.8f1 (Physics 2D package is auto disabled), 2019.2.0a7, 2019.3.0a2 (Warning window is shown but it doesn't throw an error after disabling both packages)
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
- Single particles in the Particle System randomly scale out when the simulation is playing
- Tilemap.SetTile() does not change the tiles when called from Update() in the Player
- Custom Shader Material is pink when the project is built for the WebGL platform
- New 3D URP Sample Scenes Project is created with an invalid dependency on com.unity.render-pipelines.universal-config when creating the Sample Project for the first time
- Canvas Scaler causes abnormal scaling of Canvas elements in Play Mode when UI Scale Mode is set to "Constant Physical Size" and any Editor window is moved to a differently scaled monitor and is interacted with
adam_carballo
Jan 27, 2020 15:13
Why is this "fixed in 1.0", while me being at 2019.2.9f1 with Unity.UI 1.0.0 enabled will still ask me for Physics2D?
Is it fixed on specific Unity versions instead? What's going on here?
andrewskuratov
Oct 17, 2019 09:35
The same story with Physics package.
It caused by Unity UI (unity.ugui, appeared in 2019.2) package that needs Physics built-in-package.
In 2019.1 and earlier editor versions everything was clear.
Skjalg
Sep 03, 2019 18:58
This does not happen in 2018.4 LTS version, but do happen on the latest 2019 version.
/Applications/Unity/Hub/Editor/2019.2.3f1/Unity.app/Contents/Resources/PackageManager/BuiltInPackages/com.unity.ugui/Runtime/EventSystem/Raycasters/Physics2DRaycaster.cs(16,9): error CS0246: The type or namespace name 'RaycastHit2D' could not be found (are you missing a using directive or an assembly reference?)
/Applications/Unity/Hub/Editor/2019.2.3f1/Unity.app/Contents/Resources/PackageManager/BuiltInPackages/com.unity.ugui/Runtime/UI/Core/Utility/ReflectionMethodsCache.cs(10,25): error CS0246: The type or namespace name 'RaycastHit2D' could not be found (are you missing a using directive or an assembly reference?)
/Applications/Unity/Hub/Editor/2019.2.3f1/Unity.app/Contents/Resources/PackageManager/BuiltInPackages/com.unity.ugui/Runtime/UI/Core/Utility/ReflectionMethodsCache.cs(12,25): error CS0246: The type or namespace name 'RaycastHit2D' could not be found (are you missing a using directive or an assembly reference?)
/Applications/Unity/Hub/Editor/2019.2.3f1/Unity.app/Contents/Resources/PackageManager/BuiltInPackages/com.unity.ugui/Runtime/UI/Core/Utility/ReflectionMethodsCache.cs(13,74): error CS0246: The type or namespace name 'RaycastHit2D' could not be found (are you missing a using directive or an assembly reference?)