Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a6
Issue ID
1086243
Regression
Yes
Query performance significantly dropped
How to reproduce:
1. Open attached project (BoxCastPerf.zip)
2. Open scene Scenes/SampleScene.unity
3. Open the Profiler window and switch to Timeline view
4. Play the scene
- Note that the BoxCastNonAlloc takes a really long time (2 - 4ms), a couple orders of magnitude longer than previous versions
- The exact same scene opened in an earlier version does not have this issue (the time then is 0.01ms or less)
- Reproduced with 2018.3.0a6 (33e5def6e55f)
- Not reproducible with 2018.3.0a5 (20706b925e3c)
Comments (1)
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
- "Create Empty Child" Option Creates Root Object When No Parent Is Selected
- Freeze/Crash when entering Play Mode in a specific project
- Lack of documentation regarding VFX Ray Tracing support
- Shader properties do not appear on the GameObject when switching ShaderGraphs during runtime in the Player
- Multiple '-' symbols are allowed to appear in a row when inputting '.' into a non-decimal numeric field
Peter77
Oct 03, 2018 14:21
Related forum thread:
https://forum.unity.com/threads/case-1086243-physics-query-performance-vs-2018-2.563626/