@wacov said:

1st is already possible. Oh, and you'll be able to tell the name of the object that's touching, so, yes.

For the first, you'd also be able to only start firing when the object is 'within range'. Oh, and you probably already know you can change lookAt... in the next version, you'll also be able to turn it off once started.

Could you tell me where I can find out the scripting nessicary for the "smart turret?" For example, HOW do you define object classes? HOW do you get the square root of something (square root is nessicary for the Pathagoream Therom and therefore the distance formula.)

Also, I asuming that what you mean by "you can change lookAt" refers to their use along with "if statements". If not, I don't know what you mean.

Please forgive my ignorance. I find it really hard to keep up with all the developments.

I have two questions about the next version.

First of all, will it be possible for an object to figure out which other object of a certain class is closest to it? That would be helpful in things like, turrets.

2nd, will you be able to modify the ontouching event so that the event only applies when the object is touching one particular thing? As in, a cube being set to emit stuff when it is touched by the sphere "blah" but NOT by the cone "Dorg"

Sorry that I have not been following the developments recently. I have heard that there is a new version of sketchyphysics 3x coming out, but not much else. Would it be possible for me to obtain more details? (I.e. the coding change, expected release date, etc.)

Again, sorry for not keeping up with the changes.

I feel strongly that a clear link to SP3x should be provided on the main sketchyphysics result from google search.

I have been disturbed by the number of aspiring SP users relying on Sketchyphysics 2. Not only are they missing out on a great deal, but by being unable to use our models, they will feel alienated by us.

For this reason, I believe that more should be done to indoctronate them into the fold.

This does help, but when I tried the things you told me, no luck.

I have recently started to try to make an exploding artillery shell. In theory, an impact would push an object on a slider joint, into a magnet. This would trigger an onTouch event that causes the magnet to activate, blowing the shell apart.

Now, in the "ontouch" field, I put this in: setVar("Boom",1) In the section that designates the magnet's strength, I put this in: getVar("boom")*-1000

It isn't working. What am I doing wrong?

UPDATE: Fixed. I realized the variables are case-sensitive.

It has been a while since I have been able to use sketchyphysics (you can thank a trip to mexico for that) and I must have missed out on a lot. I need to catch up with the new scripting techniques, but it is hard. The sketchyphysics wiki doesn't have a comprehensive tutorial yet (it is still somewhat obscure to me) so ya. What should I do?

For example, how do you create a variable?

Thats what I don't get. I don't think its a good idea to upload a model that will not work in the next version.

When will the final version of SP3 be released?

I need help understanding the codes used in the current models. I don't understand at all what [0,1,0] means, for example. Could someone help tutor me?

I have heard some people mention that things will be included "In the next version" or "will be included shortly." They certainly aren't referring to SPIV, so then that must mean that this isn't the last version of SP3.

Is this true?

I have been trying to make something that triggers when disturbed. I saw in a previous thread that you can't trigger objects directly by collision.

However, I was wondering if an "if" statement could check and see what the "state" (frozen, static, etc.) is and then make a decision based on that

As you may recall, one of the users posted a way you could make servos oscillate back and forth. That was back for Alpha

Math.sin(frame/3)/10

Gues what?

IT DOESN"T WORK ANY MORE! Now it is very jumpy & unreliable.

Please help me. I am not sure what to do.

The ability to assign keys to certain controllers has proven to be a great boon. However, there is one major issue: Many keys (WSAD, Space, etc.) are already assigned to a hotkey outside of Sketchyphysics. Pushing these after clicking outside the control panel or other SP window will end the simulation.

Fortunately, it is quite easy to solve this issue if you know what to do. Go to the "windows" toolbar and select "preferences." Then click on "short cuts." You will see all the preformable actions and, if applicable, their hotkeys. Go in there and disable whatever hotkeys you want to. I would recomend "space," "A," "W," "S" "D" and "Q" first.

currently, the emitter thing will only fire upwards. This is quite frustrating.

@cphillips said:

My job is keeping me from spending as much time on SP as I would like. But I will get a new version out as soon as I can.

any time estimates?

Sorry I did not get back to you earlier. I am bad about responding, as you know.

Try running the simulation....

I don't mean to be impatient, but it has been a while since the release of the 2nd alpha; when will the beta arrive?

I have found that sometimes, if you put in a too high of a number in a too small of a magnet or thruster, the simulation will freeze but never technically end.

Could you please fix this glitch.

By the way, I think that the sketchyreplay is simply too much trouble. I mean, it is the reason we had to give up making objects that automatically copy themselves, and I think you said it plays a role in what I am talking about too.

I remember a while ago Chris said that objects will be able to rapidly copy themelves with the push of a button. I don't mean the "copy body" thing. I was told that there was a code you could put in an object which told it to copy itself, when to, and in what direction...

Is that still in there?