Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3
2020.3.28f1
2021.3
2022.1
2022.2
Issue ID
1404518
Regression
No
Callback of the Triggers module does not return collider data for more than 32 colliders
Reproduction steps:
1. Open the user's attached project
2. Select the "Particle System" GameObject in the Hierarchy window
Expected result: All of the circles that the particle collides with turn green
Actual result: The circles stop turning green and the particle starts turning red past the 32nd collider
Reproducible with: 2020.3.33f1, 2021.3.0f1, 2022.1.0b16, 2022.2.0a10
Could not test with: 2019.4.38f1 ("No overload for method 'GetTriggerParticles' takes 3 arguments")
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Hi, we can't easily support more than 32 colliders without increasing the memory usage substantially for every user of this feature. This is because it is a per particle per collider matrix of information. Therefore we've decided not to prioritise fixing this at the moment.
Sorry for any inconvenience this causes.