Objects are hit in an unexpected order when casting using maxHits

Thank you for reporting a bug to Unity. After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow. We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements. Additional information: The PhysX 4.1 SDK returns an array of hits consisting of all hits that were processed for a single query (raycasst/sweep etc), this is done by eTOUCH being provided to the query filter. The returned array is not sorted by distance from origin. Now looking at our RaycastCommand when it executes it will grab all colliders the ray will hit, but the ordering is not guaranteed in any way shape or form as such providing too few max hits can end up culling some of the results. For example for a line of 10 colliders the first 4-5 colliders might be randomly ordered between indices 0 - 4 when hits are being returned. I've noticed that this isn't mentioned in the documentation. I'll make sure to get it updated. Cheers, AlexRvn.

Unity 6000.2 has reached its end of life and will not receive further updates. If you need additional fixes, please upgrade to a newer Unity version.