title: SpriteKit SKPhysicsBody broken collisions
body: <p>I have a <code>SKSpriteNode</code> which has a static body, generated from <em>concave path</em> with <code>edgeChainFromPath</code>. Let's call this node a <strong>house</strong>.</p>
  
  <p>I also have another kind of <code>SKSpriteNode</code>s which have a dynamic square body, generated with <code>rectangleOfSize</code>. Let's call this node a <strong>box</strong>.</p>
  
  <p>In my scene, the <strong>boxes</strong> are thrown aka impulsed into the <strong>house</strong> and since both of them have bodies, the <strong>boxes</strong> should collide with the <strong>house</strong> and bounce away.</p>
  
  <p>I'm scrolling the scene and therefore creating new instances of EXACTLY THE SAME <strong>house</strong> described above.</p>
  
  <p>The <strong>problem</strong> I'm having is that collisions are completely or partially broken for some <strong>houses</strong>. Some <strong>houses</strong> collide with <strong>boxes</strong> exactly as they should, some collide with <strong>boxes</strong> only on some random segments of the body, and some completely ignore collisions with the <strong>boxes</strong>.</p>
  
  <p>This problem only happens on iPad and never on iPhone. Happens both on iPad Simulator and real iPad device.</p>
  
  <p>The problem occurs completely random and on random <strong>houses</strong>.</p>
  
  <p>I also tried creating <strong>house</strong> body with <code>edgeLoopFromPath</code> but the problem remains.</p>
  
  <p>Also, I'm drawing the physics and can see that the physics body of the <strong>house</strong> is exactly as it should be.</p>
  
  <p>There is nothing else special about the scene or nodes that would be worth telling about.</p>
  
  <p>I'm using <code>SpriteKit</code> with <code>Swift</code> in <code>iOS 9</code>.</p>
  
  <hr>
  
  <p><strong>Update</strong>:</p>
  
  <p>Seems like the issue is in setting the scale on <strong>house</strong> nodes. I have to do that in order to have universal look on all screen sizes.</p>
  
  <p>Still looking for solution/workaround...</p>