I've also tried other forms of collision so it would change... see: I've tried overlapping, on collision... and even both. oh wait, I've tried even collision with solid (setting both sprites as solid, of course) and I couldn't even get the first collision in that case.

I've got to the extreme of trying platform behavior without gravity, speed etc to get the solid collision.

But in the end, megaman (wich is a random sprite I've picked just to figure how to make a loop) always ended up going out of the loop in a different way. yes, even with overlapping, wich made him go out on the funniest way possible:

overlapping with the loop slowly until he finnaly loses contact with it and fly away.

and about the angle issue pointed by deadeye: I've noted it even before I posted, because I did all I could to get outta the problem, but, as mentioned above, overlapping also takes him out, and I can clearly see that the first wall he touches is mostly the right one, since he usually's NOT touching the "ground", and he goes out even when he touches the right wall only.

(by "right" I don't mean direction, I mean the wall he must touch to change direction)

so, I got your point deadeye, since I suspected about it too. and I still suspect a bit, since I've separated the bars and left only 4 of them, and he moved like a square, and worked well.

but, for the reasons mentioned before, I'm afraid it isn't the case.

edit: maybe I should upload a pic. should I make an account in photobucket or stuff like that, or is there another way?

hey guys I'm new with construct, and I'm having troube with collisions. Not an exception, but a rule: collision is being undetected VERY OFTEN.

And my images are not pixel art stuff, my games are usually 80 or 60 fps (no slowdown or skipping).

since I couldn't find any other topic/bug report about this issue, I wonder if it's a compatibility issue.

however, I think it's written in c++, isn't it? I never tought a c++ code would have compatibility bugs

My pc is a intel dual core, pentium XP, nvidia card etc, nothing so special or rare to find about compatibility or whatever.

I'm posting here because that's not just a bug, that's a major problem that bugs me A LOT, and makes it impossible for me to make any games. I also reported the bug on the tracker, of course. And there's a cap at the tracker, that I'd like you guys to test if the collision is really only on my pc.

the report:

http://sourceforge.net/tracker/index.ph ... _id=207820

the cap for download: http://sourceforge.net/tracker/download ... id=2298967

(Keep pressing the right arrow. One time or another the sprite should fly out of the loop)

and, btw, YES, it really can stay STILL on top of another sprite (with collision all set) without detecting collisions, so it has nothing to deal with fps, it's more likely that the collision turns off at times

edit> every image I try to upload is labeled as an attack vector, so I don't have any avatar to show. sorry.