Impact

This forum is read only and just serves as an archive. If you have any questions, please post them on github.com/phoboslab/impact

1 decade ago by oravecz

While playing the latest box2d physics demo, and using the current library from git (as of today), I can only fire a particular number of bullets until the screen freezes. CPU remains pegged at 100%, no more graphics updating takes place on screen.

Using Chrome Version 19.0.1084.52

1 decade ago by Arantor

How many bullets is that?

My colleague managed to achieve the same but only once he'd got so many bullets on the screen, that even the player was totally surrounded by bullets and not a spare pixel could be seen...

1 decade ago by oravecz

I'm not sure, perhaps 300 or so.

1 decade ago by Arantor

Funny, I actually managed to recreate this today. I'm using the stock Box2D that's with the physics demo, not the upgraded version.

Now, in my one case, I can consistently create it when building a dynamically set up collision map (based on a large map I have elsewhere) and consistently it fails on creating the 513rd Box2D shape.

I wouldn't be surprised if the physics demo was also failing when the 513rd Box2D object gets created.

1 decade ago by Arantor

I actually figured out what the hell causes this.

Box2D actually declares a maxProxies value in b2.Settings which is the maximum limit of objects one can create. Going over that limit will cause it to fail with a strange and seemingly unrelated error message.
Page 1 of 1
« first « previous next › last »