What is ControllerAcc...

[EMKshadow]

Hi I'm just getting into scripting and stuff and i hear a lot of people using the controllerAcc variable. Can somebody please help the noob and tell me what exactly it does and what effect it makes on the object that has it modified?

Thanks in advance

[kilebantick]

I'm not sure, but isn't that the balue that tells you how fast the object moves, assuming that you've set the controllACC controls? Sorry, i'm not quite sure :S

[electronicboy]

it affect the geometry controller speed. so kile is right.
the geometry controller is barely used so that value is just used as a place holder to easily store a variable.

[EMKshadow]

That explains everything thanks guys

[kilebantick]

Not a problem

I don't have a need to store values in ControllerACC, because i usually use scene.my variables. HOWEVER, storing information in that field, is very good if you want to make a phunlet friendly scripted object

[Rideg]

Many people use the ControllerAcc because you rarely use it. I also use Color, RefractiveIndex, TextureMatrix, Friction, Restitution, or any other inObject variable that I won't use.

and as Kile' said: It's good if you want to make it phunlet friendly.

[EMKshadow]

Ah that's why people give it random values and have it called by random things lol. I understand it all now!

[kilebantick]

That's good

Rideg, it's not a good idea to use the Color variable, or the Texturematrix variable, as sometimes if you have quite a long string in it, it'll get deleted. Happens to me often D:

[Rideg]

I only use them to store some variables sometimes. What do you mean, does the textureMatrix get reset? :O

[electronicboy]

i think if there are too many values in the list, it is seen is invalid and is reset as a consequence.

[Rideg]

What? that sounds crazy :O

[Matten]

You can also just use e.other.data = *wathever you want*. This will make a new object variable, so no chance of deleting.

[kilebantick]

But you have to use New-Method for that to work properly, and THEN when you save the scenes, the custom variable, or "E.other.data" will completely disappear.

[Rideg]

I can't save geomID's when using new method and I've seen scenes on algobox that have theese saved in their scenes

[Mystery]

Crash course on new method in.. 3.. 2.. 1..

Code: Select all

e.this.geomID := 1;
    App.step;
    App.undo;

GeomID is now registered as an internal variable inside the object.

[Rideg]

Crash course on new method in.. 3.. 2.. 1..

Code: Select all

e.this.geomID := 1;
    App.step;
    App.undo;

GeomID is now registered as an internal variable inside the object.

When I save the scene it's not there anymore...

[Mystery]

Run the code in on-collide every time the scene runs.

[Rideg]

I did that and tryed to spawn a fixate between two objects I used e.other.geomID = * it did don work

[Mystery]

Universal Sticky Balls

Mystery

Rating:
Filesize: 43.97 kB
Comments: 7
Ratings: 3

http://www.algodoo.com/algobox/details.php?id=40098
You can either look at the code i used there to improve your own or simply use the same code.

[Rideg]

Universal Sticky Balls

Mystery

Rating:
Filesize: 43.97 kB
Comments: 7
Ratings: 3

http://www.algodoo.com/algobox/details.php?id=40098
You can either look at the code i used there to improve your own or simply use the same code.

They don't work for me :O

[Matten]

Neither for me :O

[Mystery]

What version of Algodoo are you using? I think someone said something about new method not working anymore.

[Rideg]

latest

[Mystery]

Not at all helpful.
1.7.1 or 1.7.8?

[Rideg]

1.7.8 is later than 1.7.1 right ?