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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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.