Gideros player crashed

Vallentain

A lot of times during testing.

I think there's something wrong with box2d. I tried to make one-sided platform by switching off/on the fixture's sensor, and somehow it crashed.


Now, if gideros player crashed, will it be ok on device? I exported it and tried it few times with my phone (installed apk)


No crash. All good/not?

atilim

Unfortunately, you aren't allowed to change Box2d world in PRE_SOLVE, POST_SOLVE, BEGIN_CONTACT and END_CONTACT events.

atilim

Desktop player correctly catches this error with an assertion but I think assertions are disabled on iOS/Android players.

zaniar

Try to call your switching function with delayedCall. I do that to create joint on collision. I set the delay value to 0 milisecond and it works.
But, in my case, I don't get "assertion failed" error dialog. I just get message that the world is locked. Maybe your case is different, but hope it help..

Vallentain

I didn't change the world... erm is changing fixture's sensor = changing world?


It's just kind of weird that it sometimes happen, most of the time not.

@zaniar I'll try that, thanks

ar2rsawseen

@Vallentain
I think you can't change fixture to sensor or not. You can only remove fixture and add a new one. But maybe I'm wrong.

Edited: ok I'm wrong you can do that, but I think internally it is done similar to what I said so it is changing the world

Vallentain

@ar2rsawseen
I see...

But can somebody really confirm this? What you can/can't do during collision events?
Because when I changed the sensor 9 out of 10 it was ok, but just sometime it crashed.

I fixed the code and now I never see the crash. (I still change the sensor)

ar2rsawseen

@Vallentain
Nice, so what was the problem?

Vallentain

I think... hmm when the platform's sensor is changed from true to false (non-solid to solid), the player is already colliding with the platform <-- the error is somewhere in this event, it used to crash there