problem with colision detection

Link to .capx file (required!):

dl.dropboxusercontent.com/u/169390986/PUB/error.capx

Steps to reproduce:

1. use arrow keys to rotate green box to marked "area of colision"

Observed result:

green box records colision with player but i have wierd colision detection also on the oposite side of the screen (area is marked)

Expected result:

well colision shud be only detected with player

Browsers affected:

Chrome: not tested

Firefox: yes

Internet Explorer: yes

Operating system & service pack:

Win 7 pro 64(up to date)

Construct 2 version:

126 and i just upgraded to 130

Can you reproduce this in a more reliable way? It is extremely difficult to debug issues which occur randomly. If you can make an example which shows incorrect collision on start of layout, we can probably solve the problem immediately, but with your current example it could take a very long time before we can fix it.

Hm i dont know hot to describe it more precise...

It happens every time when a green box is entering a marked area from left to right.

(from 11 o'clock to 12 o'clock movement)

See this jpeg:

<img src="https://dl.dropboxusercontent.com/u/169390986/PUB/bug%20in%20colision%20detection.jpg" border="0" />

PS:

And i see it happens if it's moved from right to left also.

:(

Updated!

dl.dropboxusercontent.com/u/169390986/PUB/error.capx

just use arrow keys when box is in the area

Ashley... do you have any update on this issue?

We're a small team and very busy, please allow 1-2 weeks for issues to be properly investigated.

Ok, ok :(

I know, patience is a virtue... that im lacking.

Your example is still extremely difficult to diagnose because it doesn't reproduce reliably, unless you press keyboard input. Can you make an example that reproduces it without requiring any user input at all? And it would be even better if nothing is moving, and it reproduces immediately on the start of the layout.

I am sorry but you must realize that mine knowledge of Construct and mine programing skills are very limited. I'w purchased licence like 2 weeks ago.

This is not something iw made... its something that is happening unexpectedly... <img src="smileys/smiley19.gif" border="0" align="middle" />   <img src="smileys/smiley19.gif" border="0" align="middle" />   <img src="smileys/smiley19.gif" border="0" align="middle" />

I'w done some changes...

Take a look at those 2 examples:

dl.dropboxusercontent.com/u/169390986/PUB/error-2.capx

dl.dropboxusercontent.com/u/169390986/PUB/error-3.capx

i'w only changed my size formula

Set size to (self.Width + rotSpeed *dt /3, self.Height + rotSpeed *dt /3)

Set size to (self.Width + rotSpeed *dt /2, self.Height + rotSpeed *dt /2)

And area of contact has shifted to the right.

Any update on this, Ashley?

I'w done some changes...

https://dl.dropboxusercontent.com/u/169390986/PUB/error-2.capx

I tried this particular example and took a look at it.

I can confirm there is indeed some sort of glitch occuring. Pretty interesting, wonder how you found it haha

I think I've managed to fix this for the next build. It was a very strange issue with the collision engine!

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

Great news guyz!

:)