Same collision code works in public release 2100, but not in 2189

The same code below works in build 2100. 

But we i run it in build 2189, it will print 3-5 times when the collision happened.

Is there any change in the box2D?

    local function onLocalCollision( self, event )         if ( event.phase == "began" ) then             if event.other.name == 'stone' and not gameOver then                 print('hit') end         end     end     player.collision = onLocalCollision     player:addEventListener( "collision", player )  

Hi Jadynut,

Nothing has changed as far as I know. And, I just tested one of my games in #2189 which uses the same essential collision functionality (local collision listener). In my tests, only one collision is registered, the same as always. So, this must be some issue in your code.

Best regards,

Brent

Brent,

Ok i will check the code again. but it works in build 2100… just don’t work in 2189…

Thank you

Still cant fix this, some code works in 2100, but not in 2189.

In 2100: only 1 ‘began’ event fired when the collision happened.

In 2189: 2-3 ‘began’ events fired every time the collision happened.

I think this should be caused by Corona updated the box 2d engine, but i dont know what they have changed…

Hi @Jadynut,

At this point, I think we’ll need you to supply a basic test case/project for this. I’ve tested it on my side and I’ve never seen this happen, nor have I heard any similar reports.

Thanks,

Brent

Hi Jadynut,

Nothing has changed as far as I know. And, I just tested one of my games in #2189 which uses the same essential collision functionality (local collision listener). In my tests, only one collision is registered, the same as always. So, this must be some issue in your code.

Best regards,

Brent

Brent,

Ok i will check the code again. but it works in build 2100… just don’t work in 2189…

Thank you

Still cant fix this, some code works in 2100, but not in 2189.

In 2100: only 1 ‘began’ event fired when the collision happened.

In 2189: 2-3 ‘began’ events fired every time the collision happened.

I think this should be caused by Corona updated the box 2d engine, but i dont know what they have changed…

Hi @Jadynut,

At this point, I think we’ll need you to supply a basic test case/project for this. I’ve tested it on my side and I’ve never seen this happen, nor have I heard any similar reports.

Thanks,

Brent