Algodoo

alrigh ive tried alot of stuff and nothing really worked so i just suggest maybe putting a small killer object at where it spawns

@Temmie -- The reason why those red circles spawn where they do is because you do not tell Algodoo where to spawn the circles, and so it automatically defaults to pos[0.0,0.0]. You can make the circles spawn at the point of collisions by adding pos := e.pos to the script. The actual script should look like the following:

(e)=>{
e.other.materialName == "fire" ? {
scene.addCircle({
radius = 0.3;
colorHSVA = [1, 1, 1, 1];
timeToLive = 0.4;
pos := e.pos
})
} : {}
}

Warning: The original way that you wrote the script caused the circles to spawn a huge number of red circles that spawned even more circles! That caused computer lag and crashing. So, change the script in each black circle as shown above AND give each one the materialName = "fire". By making these changes the scene will no longer cause lag and/or crashes!

I was going to say something similar to what Xray had to say, but he beat me to it.

I do want to say though that, from now on, try not to use regular equals signs (=) when defining variables in Scene.addObject scripts.
In my experience, this also overwrites that variable for the object spawning the other object.

For example, this script, if run inside a circle, will set its radius to 1.0 -- even though you didn't ask it to!

Scene.addCircle({
radius = 1.0
})

Even though it's inside of a scene.addCircle script, the = operator is also overwriting the circle's own radius.

Instead, use the := operator.
The := operator always tries to define a new variable if possible rather than redefining an already existing one.

Scene.addCircle({
radius := 1.0
})

This script will not resize the circle being used to spawn the new circle.

I hope this helps!

Very well stated, Little!

Thank you