Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0b2
Issue ID
1085279
Regression
No
Non-allocating physics queries do not work anymore
To reproduce:
1. Open the attached project (BugReport.zip)
2. Open the "Scene" scene
3. Enter Play mode
4. In the console, observe that non-allocating queries return 0 results
Expected: non-allocating physics queries return the same results as the regular queries
Reproduced in 2017.4.12f1, 2018.1.9f2, 2018.2.10f1, 2018.3.0b2, 2018.3.0b4, 2019.1.0a2
Comments (1)
-
Squidcor
Oct 03, 2018 10:51
Not sure how this can be classified as by design? Is Unity just going to remove the non-allocating API seeing as it doesn't work anymore?
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
There is a problem with the code: The initial assignment of "hits" and "colliders" allocates an empty array with no entries (new RaycastHit[0]). Because the query being used a non-allocating one, the number of entries in the array has to be allocated manually.