Search Issue Tracker
By Design
Votes
0
Found in
1.4.4
Issue ID
UUM-134775
Regression
No
Errors are thrown when Unity Physics package is installed
How to reproduce:
1. Open the attached project "IN-131228"
2. Observe the Console
Actual result: Errors are present
Expected result: Console has no errors present
Reproducible with: 1.4.4 (6000.0.67f1, 6000.5.0a6)
Not reproducible with: 1.4.3 (6000.0.67f1), 1.4.4 (6000.3.7f1, 6000.4.0b7)
Fixed in: 6.5.0 (6000.5.0a5)
Reproducible on: Windows 11 Enterprise
Not reproducible on: No other environments tested
Note:
Library\PackageCache\com.unity.physics@4ad4f3485fc7\Unity.Physics\ECS\Base\Aspects\RigidBodyAspect.cs(22,54): error CS0246: The type or namespace name 'IAspect' could not be found (are you missing a using directive or an assembly reference?)
Library\PackageCache\com.unity.physics@4ad4f3485fc7\Unity.Physics\ECS\Base\Aspects\ColliderAspect.cs(14,53): error CS0246: The type or namespace name 'IAspect' could not be found (are you missing a using directive or an assembly reference?)
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.