Scripting Bug?

[losc00]

When I put something into one of the boxes in the scripting menu for an object.
e.g.
The simulation works just as it is supposed to, until I save the simulation and load the saved file. If I load the saved version the {variable} is changed to whatever the default value for the parameter is, in this case 2.

Am I doing something wrong here?

[Mystery]

When you use {rDensity) the variable will be saved to the config file, this is bad. Instead Use scene.my.rDensity, to make a scene.my variable put

Code: Select all

Scene.my.Test = 10


Into the console

Then to use this variable just put in

Code: Select all

{scene.my.test}


Scene.my will save the variable into the scene which is safer for every one.

[losc00]

I see, thanks.
However, even after changing the syntax to scene.my.rDense the problem still exists.
When I save and load the project the Density section of the object script settings has reverted to the default value (2) from what I originally put there ({scene.my.rDense}).

[standardtoaster]

Actually, you are not doing anything wrong with the custom variable. This is a known bug and is trying to be fixed.

[Frank]

Actually, you are not doing anything wrong with the custom variable. This is a known bug and is trying to be fixed.

Indeed. Algodoo also has issues saving geometry-specific custom variables. My guess is that it has something to do with a rogue error-fixing routine. This was one of the first bugs they acknowledged, so I'd bet it will be fixed in the first update.

[Joel]

Yes, this is a known issue and it will be fixed. For now, make sure that the variable is not the default value of the attribute.