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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Add comment