Browse Search Popular Register Upload Rules User list Login:
Search:
Sierpinski cube triangle fractal

Image:
screenshot of the scene

Author: homieeee

Group: Default

Filesize: 20.91 kB

Date added: 2014-12-09

Rating: 5

Downloads: 500

Views: 234

Comments: 9

Ratings: 1

Times favored: 0

Made with: Algodoo v2.1.0

Tags:

Scene tag

Enjoy :)

Also 10 iterations is impossible in algodoo... as it is a 32 bit program and can only use 2 GB of ram and 10 iterations needs a lot more than 2 GB :lol:
Last edited at 2014/12/09 19:51:25 by homieeee
Please log in to rate this scene
edit
Similar scenes
Title: Sierpinski Triangle
Rating: 5
Filesize: 46.13 kB
Downloads: 668
Comments: 0
Ratings: 1
Date added: 2020/09/12 11:05:12
Made with: Algodoo v2.1.0
Rating: rated 5
download
Title: Sierpinski Carpet Fractal
Rating: 5.8889
Filesize: 150.47 kB
Downloads: 902
Comments: 6
Ratings: 3
Date added: 2017/03/27 09:45:32
Made with: Algodoo v2.1.0
Rating: rated 5.9
download
Title: Sierpinski Triangle
Rating: 6.3333
Filesize: 1.26 MB
Downloads: 264
Comments: 1
Ratings: 3
Date added: 2008/07/26 13:36:49
Made with: Phun
no image found for this scene
Rating: rated 6.3
download
Title: Sierpinski's Triangle
Rating: 5
Filesize: 143.96 kB
Downloads: 254
Comments: 2
Ratings: 1
Date added: 2016/05/07 06:03:03
Made with: Algodoo v2.1.0
Rating: rated 5
download
Title: Sierpinski Triangle
Rating: 5
Filesize: 75.05 kB
Downloads: 582
Comments: 6
Ratings: 1
Date added: 2020/05/12 15:38:26
Made with: Algodoo v2.1.0
Rating: rated 5
download
Title: neat fractal
Rating: 5
Filesize: 100.15 kB
Downloads: 446
Comments: 0
Ratings: 1
Date added: 2017/08/06 16:15:25
Made with: Algodoo v2.1.0
Rating: rated 5
download
Interesting scene! Good job. :tup:


Just a suggestion: Rather than use density = 0 to delete a geometry, it is much better to use Scene.RemoveEntity(entity). The reason (as far as I understand it) is because when you use density = 0, Algodoo does not actually remove all of the deleted geometry, as it leaves some remnants of it in memory, which could clutter up memory if you delete a lot of them (as you do in this scene). ;)
Thanks you Xray!

And that explains why the memory never freed up. But for some reason every time i call scene.removeEntity(entityid) i get an error "RemoveEntity called on non-entity: "
Not (entityid), but rather: (entity). You added something extra "id" that doesn't belong there! :lol:
Doesn't seem like either of them work:bonk:
With just scene.removeEntity(entity) its says "RemoveEntity called on non-entity: null"
Use timeToLive = 0.0 and let Algodoo worry about it.
I did but it still has a memory leak so there's nothing I can do about it.
Yeah, I forgot about timeToLive = 0. In fact, I use that technique more than any other for deleting objects, and it has never caused any problems. I don't know what else can be done for your scene beyond those suggestions. Sorry...
Don't worry about it Xray it seems to just be a bug with algodoo!
Mem leak happened then deleting objects with code. Nothing we can do with it.
:x