Search Issue Tracker
Fixed
Fixed in 6000.3.0b7, 6000.4.0a4
Votes
0
Found in
6000.3.0a5
6000.4.0a1
Issue ID
UUM-122002
Regression
No
Missing API for Shape vs Shape Intersection
For the new low-level 2D physics that landed in 6000.3.0a5, we included a bunch of geometry vs geometry query methods which allow the calculation of a contact manifold, fully describing the contact details using the "Intersect" method.
Unfortunately we didn't include the shape vs shape query methods:
- {{PhysicsQuery.ShapeAndShape}}
- {{PhysicsShape.Intersect}}
These are missing pieces so without these, it's extremely cumbersome for a user to find an intersection as they have to get the shape geometry from each and then figure out which combination of query methods to use in the PhysicsQuery type.
Today I had a report of this where a user wanted to perform a shape vs shape intersection test and the resultant code I provided as an example is quite verbose.
The addition of these two methods completely solve that by abstracting the shape types away. This should've landed in 6000.3.0a5 but it was an oversight on my part.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Navigating Prefab Components in Overrides window shows rendering artifacts in the Editor
- Prefab Overrides window cuts-off Component labels across multiple Components
- Opening Memory Settings documentation from Project Settings window opens missing page
- Animated GameObjects ignore Shader keywords when running on VisionOS Player with Polyspatial
- Quickly clicking "Open query in Search Window" in the Hierarchy twice opens the two Search tabs at the same time
Add comment