Got it. Thanks for the pointer.
> On 18 Sep 2018, at 13:32, Tomasz Wlostowski wrote:
>
> On 18/09/18 12:17, Jeff Young wrote:
>> When we check for collisions we do it first with the
>> worst-case-clearance value (m_maxClearance). I imagine this is so that
>> we can search the RTree
On 18/09/18 12:17, Jeff Young wrote:
> When we check for collisions we do it first with the
> worst-case-clearance value (m_maxClearance). I imagine this is so that
> we can search the RTree uniformly.
>
Hi Jeff,
Yes, that's ^^^ the reason.
> But don’t we then have to check each collision for
When we check for collisions we do it first with the worst-case-clearance value
(m_maxClearance). I imagine this is so that we can search the RTree uniformly.
But don’t we then have to check each collision for actual clearance violation
(ie: with the actual, not worst-case clearance values)?
3 matches
Mail list logo