Freeze with Physics

This topic has 5 replies, 2 voices, and was last updated 4 years, 7 months ago by Yuri Kovelenov.

Viewing 6 posts - 1 through 6 (of 6 total)

Author

Posts
2019-09-20 at 2:00 pm #19067

brownie
Participant

Hi, This is my second and hopefully the last problem I have with my upcoming configurator. When I move my furnitures and play a couple of seconds with the collision feature I made with puzzles, I get a frozen WebGL screen with this message in the console :

uncaught exception: abort(“Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 67108864, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or (4) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0 “). Build with -s ASSERTIONS=1 for more info. ammo.js:316:300
sa http://localhost:8668/applications/leconfigurateur/ammo.js:316
Fa http://localhost:8668/applications/leconfigurateur/ammo.js:13
enlargeMemory http://localhost:8668/applications/leconfigurateur/ammo.js:28
Go http://localhost:8668/applications/leconfigurateur/ammo.js:53
ic http://localhost:8668/applications/leconfigurateur/ammo.js:50
bt http://localhost:8668/applications/leconfigurateur/ammo.js:53
Sp http://localhost:8668/applications/leconfigurateur/ammo.js:53
q http://localhost:8668/applications/leconfigurateur/ammo.js:347
createPhysicsBody http://localhost:8668/applications/leconfigurateur/visual_logic.js:1885
forEach self-hosted:266
createPhysicsBody http://localhost:8668/applications/leconfigurateur/visual_logic.js:1862
init http://localhost:8668/applications/leconfigurateur/visual_logic.js:4648
moveCb http://localhost:8668/applications/leconfigurateur/visual_logic.js:1186
Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 67108864, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or (4) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0

Maybe some sort of un infinite loop in my puzzles, but I remember someone had this kind of message with an older version of Verge3d.

Thanks for any help (and for the fast answers to my previous posts in this section) :)

2019-09-20 at 2:30 pm #19070

Yuri Kovelenov
Staff

Hi,

This memory overflow error hints that your are using too high-poly meshes as physical objects. Try using Box shapes instead of Mesh whenever possible.
https://www.soft8soft.com/docs/manual/en/puzzles/Physics.html#create_physics_body

Chief 3D Verger | LinkedIn | Twitter

2019-09-20 at 2:38 pm #19072

brownie
Participant

Thank you,

I actually use Box but I have a lot of “hidden” furnitures which are listed as collision objects. Do you think Physics is calculating collision for hidden objects ?

2019-09-20 at 2:42 pm #19075

Yuri Kovelenov
Staff

Yes is does! Physics bodies are independent entities.

Chief 3D Verger | LinkedIn | Twitter

2019-09-20 at 2:46 pm #19076

brownie
Participant

Ouch. It means that while I’m gently playing with 2 or 3 furnitures, more than 30 others are fighting in silence !

Thank you. Im’ gonna try to activate Physics only for the elements actually in scene, and let you know if I get rid of the error message.

2019-09-20 at 3:11 pm #19077

Yuri Kovelenov
Staff

Sure, let us know how it goes!

Chief 3D Verger | LinkedIn | Twitter
Author

Posts