[Question] Lifetime

[Matten]

Does someone know how to give a geom a lifetime? I'm working on a fire simulator and I want that the fire"balls" dissapear after 5 sec. They don't touch something, so with onCollide it can't.

[KarateBrot]

Declare a new variable like "scene.my.time" and then use something similar:

Code: Select all

(scene.addCircle{pos := app.mousepos; scene.my.time = sim.time}).density  = {sim.time - scene.my.time <= 5 ? {2} : {0}}


[tatt61880]

Declare a new variable like "scene.my.time" and then use something similar:

Code: Select all

(scene.addCircle{pos := app.mousepos; scene.my.time = sim.time}).density  = {sim.time - scene.my.time <= 5 ? {2} : {0}}


Be careful, density = 0 will crashes Phun. It works well only with Algodoo.

[KarateBrot]

yeah but we're in the algodoo forums and he didn't say he's using phun, right?

for phun use airfrictionmult = NaN instead of density = 0

[Matten]

That's a good script, but what I want to have is that every "ball", deletes (I use a simple delete script with no collide and invisible) 5 seconds after his creation. So not that all balls dissapear after 5 sec.

[KarateBrot]

so then just use object variables

Code: Select all

(scene.addCircle{pos := app.mousepos; controlleracc := sim.time}).density  = {sim.time - controlleracc <= 5 ? {2} : {0}}


but it only works if you go to the scripting menu of each circle and press enter after you clicked into the density line. maybe a bug?? it's because of "sim.time - controlleracc <= 5". every time there is more than one variable it's very bitchy.

[Matten]

I've tried the script and it didn't work like you said. I will try it on another way.

[Versieon]

I tryed this in onLaserhit

Code: Select all

(e)=>{
    (scene.addCircle({
        pos := e.pos;
        eval("scene.my.my" + e.geom.controllerAcc + " = sim.time")
    })).density = {sim.time - eval("scene.my.my" + e.geom.controllerAcc) <= 5 ? {2} : {0}};
    e.geom.controllerAcc = e.geom.controllerAcc + 1
}

But instead of creating new variables each time, it shut down Algodoo and didn't record anything in the log file...

[Chronos]

Maybe it has to do with the quotes around scene.my.my?

[tatt61880]

so then just use object variables

Code: Select all

(scene.addCircle{pos := app.mousepos; controlleracc := sim.time}).density  = {sim.time - controlleracc <= 5 ? {2} : {0}}


but it only works if you go to the scripting menu of each circle and press enter after you clicked into the density line. maybe a bug?? it's because of "sim.time - controlleracc <= 5". every time there is more than one variable it's very bitchy.

Could you make a bug report for this?
This bug were reported by one Japanese several days ago.
These days, I've searched this forum about this bug.

This bug seems to be something to do with "namespace".

I found a same kind of bug report.
viewtopic.php?f=11&t=112&p=946#p946
(
Declaring global variable named "size" etc. is not good because of name conflict. This bug were fixed by v1.6.4.

* Global variables with names conflicting with entity attributes (e.g. "color", "pos" etc) no longer interferes with deserialization

)

[Rrobba]

Declare a new variable like "scene.my.time" and then use something similar:

Code: Select all

(scene.addCircle{pos := app.mousepos; scene.my.time = sim.time}).density  = {sim.time - scene.my.time <= 5 ? {2} : {0}}


Be careful, density = 0 will crashes Phun. It works well only with Algodoo.

This. If you use Phun then it will most probably crash instantly so be careful. If you use Algodoo though you should be OK.

[KarateBrot]

This. If you use Phun then it will most probably crash instantly so be careful. If you use Algodoo though you should be OK.

That's what tatt already said

[Matten]

To prevent useless discussions, I use Algodoo.

[KarateBrot]

that's gonna be very interesting for your fire simulator
http://www.algodoo.com/forum/viewtopic.php?f=13&t=1322&p=26937#p26885

[Matten]

I think this will work, but at the moment Algodoo is very slow (first it wasn't). So I haven't tried it yet.

[Rideg]

*Bump*

Well perhaps you've solved this already but I'm doing a lighter that spawns circles adn make them collide with a box that changes their collision and triggers their onCollide. The circles have 1 sec before they disappear(density = 0); Here's the onCollide script it might help

Code: Select all

onCollide := (e)=>{
                e.this.controllerAcc = e.this.controllerAcc + sim.time;
                e.this.density = {sim.time >= controllerAcc ? {0} : {0.001}};
                e.this.onCollide = (e)=>{}
            }

ControllerAcc is the time it should "live" then I add the "sim.time" variable and make an "wannabe" if-statement that's controlling when the density should be 0. And it also disables the onCollide of the circle to prevent add lifetime to the circle.

Hope it'll work works fine for me

[Matten]

Thank's for help, but I've found another (better) way. I have a laser in the fire balls with a time script. With this way I've also made a cluster bomb.

Scripted cluster bomb

Matten

Rating:
Filesize: 9.07 kB
Comments: 3
Ratings: 3

[Rideg]

okey well it lagged my computer shitless with lasers that's why I declared the dynamic variables via onCollide I'll check that scene now