Ill show you an error!
This is in reply to adrianlattes: “Phun error” (I did not get the error)
This only happens in Phun, and can be sorted by fixing the green box to the background?!
But in Algodoo we have the problem of unnecessary memory usage. If you create an object and kill it in any possible way:
Kill: =True
onCoillide = (e) => {e.other.density:=0}
onCoillide = (e) => {e.other.airFrictionMult = NaN}
Alternately:
App.maxUndo:=1
Windows memory cleaning software…
The memory is not released or recycled; this is a problem for all spawn engine developers.
Anyone with a spawn engine watch the scenes info and check your Task manager/processes, you will see Phun/Algodoo memory continue to rise even thought you do not have any changes to the object count. Eventually all spawn engines and any scene that creates and kills objects will error or stop working, when the memory reaches 2GB, and believe me it dose not take long on high RPM.
I’m very interested in starting competitions to finding a solution to this problem or challenging the developers to fix the problem. My only solution was to re-use objects by moving them to a holding place then bringing them back, so never kill them. (It sucks!)
I love this software, and the community it has created. After searching the web for a suitable replacement found OE-Cake, Phyzios, Roblox and Blender totally unsatisfying in comparison to Algodoo.
Please fix this problem!
.png)
