Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.5.0a6
6000.5.0a7
6000.6.0a1
Issue ID
UUM-135232
Regression
No
Updating a project with Unity Physics samples throws obsolete errors in the console with no information to update the samples
Steps to reproduce:
- Create a new project on 6000.5.0a5
- Open Window > Package Management > Package Manager
- Navigate to Sources > Unity Registry tab in the left
- Search for Unity Physics package
- Install the package
- In the package description window open Samples tab
- Import the Custom Physics Authoring sample
- Observe the console of multiple obsolete warning
- Update the project to 6000.5.0a6
\\
Actual results:
Obsolete errors in the console with no information how to solve the errors.
Expected results:
An information pop up or console entry appears to inform user to update the samples
\\
Reproducible with versions:
6000.5.0a6, 6000.5.0a7
Not reproducible with versions:
6000.0.68f1, 6000.3.10f1, 6000.4.0b10
\\
Tested on (OS):
MacOS Sequoia 15.7.3
\\
Notes:
- Reimporting the samples fixes the errors
Assets/Samples/Unity Physics/6.5.0/Custom Physics Authoring/Unity.Physics.Custom/Bodies/BakingSystems/PhysicsBodyBakingSystem.cs(67,21): error CS0117: 'PhysicsCompoundData' does not contain a definition for 'ConvertedBodyInstanceID'
Assets/Samples/Unity Physics/6.5.0/Custom Physics Authoring/Unity.Physics.Custom/Bodies/BakingSystems/PhysicsShapeBakingSystem.cs(67,90): error CS0117: 'BakeStaticRoot' does not contain a definition for 'ConvertedBodyInstanceID'
Assets/Samples/Unity Physics/6.5.0/Custom Physics Authoring/Unity.Physics.Custom/Bodies/BakingSystems/PhysicsShapeBakingSystem.cs(75,17): error CS0117: 'ColliderInstanceBaking' does not contain a definition for 'AuthoringComponentId'
Assets/Samples/Unity Physics/6.5.0/Custom Physics Authoring/Unity.Physics.Custom/Bodies/BakingSystems/PhysicsShapeBakingSystem.cs(87,27): error CS1061: 'ColliderInstanceBaking' does not contain a definition for 'ConvertedAuthoringInstanceID' and no accessible extension method 'ConvertedAuthoringInstanceID' accepting a first argument of type 'ColliderInstanceBaking' could be found (are you missing a using directive or an assembly reference?)
Assets/Samples/Unity Physics/6.5.0/Custom Physics Authoring/Unity.Physics.Custom/Bodies/BakingSystems/PhysicsShapeBakingSystem.cs(88,27): error CS1061: 'ColliderInstanceBaking' does not contain a definition for 'ConvertedBodyInstanceID' and no accessible extension method 'ConvertedBodyInstanceID' accepting a first argument of type 'ColliderInstanceBaking' could be found (are you missing a using directive or an assembly reference?)
Assets/Samples/Unity Physics/6.5.0/Custom Physics Authoring/Unity.Physics.Custom/Bodies/BakingSystems/PhysicsShapeBakingSystem.cs(114,25): error CS0117: 'PhysicsCompoundData' does not contain a definition for 'ConvertedBodyInstanceID'
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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 (6000.6.X):
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.