SP3x Apr3 version.

MrPlanet

THANK YOU SO MUCH FOR A ZIP VERSION!!!!

Sgt.A.Johnson

Man thats cool. I want a go but ill never remember code to do it

BTM

2 things: one, Is that when you go back to edit scripts sometimes the spaces will be double, and if that happens to one script several times,it can make it harder to read. Can that be fixed?

also, is there a way to have a OnTouch function work with specific objects?

CPhillips

@unknownuser said:

Ooooooooooohhhhhhhh that looks great. Will they be able to be emitted? And Can anything that collides with a "joint" connect to it?

Not at this time. And yes.

CPhillips

@unknownuser said:

2 things: one, Is that when you go back to edit scripts sometimes the spaces will be double, and if that happens to one script several times,it can make it harder to read. Can that be fixed?

I havent seen that. It might be Mac specific. Can you give me the steps to reproduce it.

@unknownuser said:

also, is there a way to have a OnTouch function work with specific objects?

Not yet.

KDSDESIGN

i installed it, but when i press play it says im still using alpha...?

Wacov

Look in the UI; when you have an object selected, if 'onTouch' and 'onTick' are shown as options near the bottom, then don't worry. If they aren't, you'll have to ask C Phillips what to do next.

If they are there, then don't be concerned about the version display, mine still says RC1.

CPhillips

Sorry there has been no new version in a while. Based in large part to the feedback from this version. I am going to make a few changes.

getVar/setVar will continue to work, But I am going to make a change that will allow you to use what ruby calls member variables. In next version instead of this:

setVar("count",getVar("count")+1)

You can do this:

@count=@count+1

or even

@count+=1

Another feature of this is that each object can have its own copy of the variable. So you could have 3 objects with different values in "@count". If you truly want all object to look at the same copy you can use "@@count"

While handy all by itself this will also make it possible for scripts to know a lot more about the objects. For example in the onTouch you could use:


if(touching.name=="sphere") 
g=touching.copy #make a copy of the sphere
g.magnetic=true; #make copy magnetic.
end

"touching" is a new command for onTouch scripts that gives you access to the object that touched. So you could look at its name or location or color or whatever.

Also you can interact with the object.
"g=touching.copy" means make a copy of the touching object and store it in temp variable "g".

"g.magnetic=true" Someone asked to be able to make emitted objects magnetic and this is how you would do it.

Its going to take a bit before it is ready but it will be worth it.

Wacov

WooHoo! With the new variables, will @foo be usable by only one script, or every script within an object? Oh and could you let the simulation know more about what an object is doing; like, 'sphere.speed' to find an object's speed?

FredIIVX

I was wondering, is there any way to put scripts in the white boxes? Because I was trying to set the ratio of a gear to something like getVar('Ratio') but it won't let me type letters in any of the white boxes, so I tried copying getVar('Ratio') into it, it lets me do that but it's gone the next time I open the UI box.

Sgt.A.Johnson

@frediivx said:

I was wondering, is there any way to put scripts in the white boxes? Because I was trying to set the ratio of a gear to something like getVar('Ratio') but it won't let me type letters in any of the white boxes, so I tried copying getVar('Ratio') into it, it lets me do that but it's gone the next time I open the UI box.

you can only put script in blue boxes not white