Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0b8
2019.1.0a1
Issue ID
1099137
Regression
No
[General] Physics.RaycastNonAlloc returns empty/null results array when a nearby objects' collider is re-enabled
How to reproduce:
1. Open attached project "Bug Raycast changing mesh colliders.zip" and scene "SampleScene"
2. Enter Play Mode
3. In Hierarchy window, right-click -> 3D Object -> Cube
4. In Inspector window, re-enable either "Box Collider" or the whole gameObject and immediately observe Scene view
Expected result: the white line is present
Actual result: the white line turns off for a split second
Reproducible with: 2017.4.16f1, 2018.3.0f2, 2019.1.0a12
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
- URP ShadowCaster2D is misplaced and distorted when used with rotated Perspective Camera
- UI mesh is drawn twice when two cameras are used
- The Scene view top menu bar disappears when any Draw Mode other than "Wireframe" is selected in the specific project with a corrupted Material
- TabView.tabClosed EventHandler passes the wrong tab index as parameter when closing a tab from oldest to newest order
- Rigidbodies clip through terrain and snap back up when Heightmap Resolution is bigger than the terrain size
Resolution Note:
This fix is available with PhysX 4.1 and won't be back-ported.