[Bug] Collision Arbiter Normals Swapped

[EduardoLopes]

While making my game for ludum dare 34, i found a bug, at first i thought it was my code, then i found how to fix it and i guess it is a nape bug.

The api docs says that CollisionArbiter.normal will always point from arbiter's shape1 towards shape2, but doesn't seem to work like this every time, it depends on the order that the shapes are being instantiated.

I made a test. Here's the source code and you can see the test running online. There's some comments in the code explaining what's happening.

Hope this will help figure out what is happening. And if this is not a bug, please help me fix my code, i put a lot of time into this issue trying to fix it without touch nape code.

[EduardoLopes]

I fixed this by checking if the id of the shape1 is equal the id of the shape it should be, if not, i invert the normal.

[alamboley]

Yeah, I'd the same issue too! Having a crazy one-way platform.

[alamboley]

@deltaluca please would you mind to provide a fix & make a release build?

[alamboley]

@EduardoLopes just by curiosity, why closing this?

[EduardoLopes]

@alamboley I was cleaning up my issue box and this is there since 2016. I don't feel like this will ever be fixed.

[alamboley]

@EduardoLopes yup sadly :( thanks for the answer 👍

[EduardoLopes]

yea :(

[alamboley]

Perhaps it has been fixed there, but can't confirm:

• https://github.com/shirogames/hxnape
• https://github.com/HaxeFlixel/nape-haxe4

[Gama11]

nape-haxe4 only fixes compilation with Haxe 4 so far, nothing else. From the commit history I doubt that hxnape does more than that too.

[MSGhero]

I think you summoned him from being too busy? https://www.newgrounds.com/bbs/topic/578434/2044#bbspost26513818_post_text