Animmaniac's Forum Posts

• You do not have permission to view this post

• You do not have permission to view this post

• You do not have permission to view this post

• You do not have permission to view this post

• You do not have permission to view this post

• • Animmaniac
  • 
  • • Joined 18 Mar, 2010
    • 
    • 36 topics • 711 posts
  • 1

  • 30 May, 2013
  • Quote

  I made a stripped down version some days ago but didn't had the time to post it. I tested and confirmed this odd behavior involving rotated layers and collision.

  It's probably fixed already, but I will leave it here anyway in case it can be of any help:

  Collision Bug Repro 01

• You do not have permission to view this post

• You do not have permission to view this post

• You do not have permission to view this post

• You do not have permission to view this post

• You do not have permission to view this post

• • Animmaniac
  • 
  • • Joined 18 Mar, 2010
    • 
    • 36 topics • 711 posts
  • 1

  • 13 May, 2013
  • Quote

  I would approach it like this:

  Family Trick Demo 02

  Also depending on how your objects are setup it's better to compare the heights using a defined threshold, since sometimes they can be slightly different due to rounding errors.

• You do not have permission to view this post

• You do not have permission to view this post

• • Animmaniac
  • 
  • • Joined 18 Mar, 2010
    • 
    • 36 topics • 711 posts
  • 1

  • 11 May, 2013
  • Quote

  Maybe you are right, but I'm not currently aware if C2 does this optimization of not checking already checked pairs in reverse order.

  I used to believe it just did two nested loops checking every instance from Family1 Vs every instance of Family2, since the most usual cases of use doesn't involve checking the same instances.

  In this case 'Family On Collision with Family' would check X-X, X-Y, X-Z, Y-X, Y-Y, Y-Z, Z-X, Z-Y, Z-Z.

  I'm in doubt now about what really happens under the hood.