Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.4f1
Issue ID
UUM-42920
Regression
No
[Unity Physics] Joints fail to follow physics when project uses Unity Physics
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/1. Hello World/HelloWorld.unity” Scene
3. In Hierarchy enable “HelloWorldSubscene”
4. In Hierarchy, expand "LegacyPhysics” and “ABSpherical"
5. Make sure that ABSpherical_LFF, ABSpherical_FLF and ABSpherical_FLL is enabled in Hierarchy
6. Enter the Play Mode
Expected result: All Joints move according to physics
Actual result: 3 Joints from step 5 will move randomly
Reproducible with: 1.0.8 (2022.3.4f1), 1.0.11 (2022.3.4f1)
Could not test with: 1.0.0-pre.65 (2022.3.4f1) (error CS0006: Metadata file 'Library/PackageCache/com.unity.ext.nunit@2.0.3/net35/unity-custom/nunit.framework.dll' could not be found)
Reproduces on: Windows 10 Enterprise 21H2
Notes:
- Project has custom angular joint with 1 locked axis and 2 free axis
- If Physics Settings in HelloWorldSubscene is set to Havok everything works, however, the issue reproduces when it is set to Unity Physics
- All combinations make the simulation run amok and end in NaN
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
We strongly suggest updating the project to either dots-1.1 or dots-1.2 for better quality, such versions contain a fair amount of bug fixes. Please report back if the problem persists so that we can fix it on our end in newer versions.
Thank you!