Problem with airFrictionMult = NaN

[art-e-fact]

The following script spawns circles that should disappear after some collisions through "e.this.airFrictionMult = NaN". This does seem to work fine, but at the same time every loose or hinged object, regardless if it is in the same collisiongroup or not, does disapoear too. Is there any way to avoid this?

Code: Select all

(e)=>{
     scene.addCircle({         
          color := [0.2, 0.2, 0.2, 0.0];         
          size := 0.5;         
          density := 0.005;         
          pos := e.pos;         
          collideSet := 1;         
          controllerAcc := 0.05;         
          OnCollide := (E)=>{{controlleracc > 0.01} ? {controlleracc = controlleracc - 0.01} : {e.this.airFrictionMult = NaN}}})}

[standardtoaster]

AFAIK this is a known bug. Instead of using airFrictionMult try using density = 0.

[art-e-fact]

That works great, thanks alot.

[standardtoaster]

Your welcome. Although, I don't know why airFrictionMult set to NaN delets everything that isn't attached to the background.

[link145632]

well if im correct this makes the air kinda go crazy because phun reads NAN as 0 and it is a irregular number, as so it doesent know what to do and causes it to displace evreything intiul it gets to the "black border of death"

[RA2lover]

nope. you can avoid it by having it to have its collision group removed before setting airfrictionmult to NaN...
but remember air needs to be on for it to work.

[KarateBrot]

well if im correct this makes the air kinda go crazy because phun reads NAN as 0 and it is a irregular number, as so it doesent know what to do and causes it to displace evreything intiul it gets to the "black border of death"

NaN isn't read as 0 in Phun or Algodoo. NaN is a defined value. It's the short form for "not a number". For example you get NaN if you divide integer values with 0 for example 3/0 = NaN.
If airfrictionmult is 0 the geometry is just not affected by air friction.

[RA2lover]

but is still affected by air buoyancy