Browse Search Popular Register Upload Rules User list Login:
Search:
9 VERY SMALL SPAWN ENGINES! NO LAGG?

Image:
screenshot of the scene

Author: dev8state

Group: Default

Filesize: 315.34 kB

Date added: 2010-06-15

Rating: 5

Downloads: 603

Views: 919

Comments: 5

Ratings: 1

Times favored: 0

Made with: Algodoo before v1.8.5

Tags:

Scene tag

Dose this mean small is good? :tup:
Please log in to rate this scene
edit
Similar scenes
Title: Some Rotary Spawn Engines
Rating: 5
Filesize: 84.06 kB
Downloads: 269
Comments: 0
Ratings: 1
Date added: 2010/03/21 02:38:42
Made with: Algodoo before v1.8.5
Rating: rated 5
download
Title: Spawn engine turbo
Rating: 5
Filesize: 307.91 kB
Downloads: 1488
Comments: 0
Ratings: 1
Date added: 2014/10/18 23:02:29
Made with: Algodoo v2.1.0
Rating: rated 5
download
Title: pick-up with universal engine
Rating: 5
Filesize: 31.84 kB
Downloads: 395
Comments: 0
Ratings: 1
Date added: 2010/03/28 19:15:25
Made with: Algodoo before v1.8.5
Rating: rated 5
download
Title: Rocket Contest (Difficult)
Rating: 5
Filesize: 43.37 kB
Downloads: 464
Comments: 4
Ratings: 1
Date added: 2011/05/16 16:23:09
Made with: Algodoo before v1.8.5
Rating: rated 5
download
Title: RealScale 6cyl Spawn Engine w/ gears
Rating: 5.8889
Filesize: 143.21 kB
Downloads: 2674
Comments: 3
Ratings: 3
Date added: 2019/08/03 23:36:40
Made with: Algodoo v2.1.0
Rating: rated 5.9
download
Title: Rocket + Moonlander
Rating: 5
Filesize: 220.38 kB
Downloads: 437
Comments: 5
Ratings: 3
Date added: 2009/03/04 22:50:45
Made with: Phun
Rating: rated 5
download
This scene is a response to:
Title Author Rating Downloads Comments Date added
VERY SMALL SPAWN ENGINE! (Response to Tinyengine v2) dev8state 5.4 (2 votes) 857 3 2010/06/15 12:48:53
show grid
May need to load this a few times before things don't fall off? Also even with no lag, i got an out off memory error>? Perhaps its a glitch? :s
Why am loosing memory on this one? )|(
Well it seams that Algodoo dose not release memory after an object is deleted. So the hole idea about spawn engines will always result in an out of memory if you let it run a long time.

The best way would to not delete them but to transport them somewhere and then on collision transport them back. So i recon i will start to look into spring/bounce and magnet motors... :/
Hmm dev8state I didnt't know that! No wonder a seemingly reliable spawn engine craps out after a long run:bonk: I have been making collision change engines which seem to work well
@Gent: I found out its because when you destroy an object its memory is not reused, so keeps going up until you reach 2 gig memory usage, then it stops making new objects or crashes.

Best to keep objects down or reuse them! :o

perhaps rather than kill the object set its position (relevant to your engines position) to a different location, then on collide set scene.my.explosion to there your collision is and set pos in the object to back to scene.my.explosion...