Don't you mean the physical geometry? That would be pretty useful.

I think mass is determined by density and volume, but weight is determined by mass and gravity. Objects in a weightless environment still have mass... but maybe you could insert a tool that tells you an object's weight, in the thruster power it would take to make it neutrally 'bouyant' in the air?

Oh and can you make the camera reset remember the field of view setting?

Some useful stuff (in the new syntax):

joy("leftx")
joy("lefty")
joy("rightx")
joy("righty")
joyRY (Analogue triggers on a 360 style pad)

joybutton("a,b,x,y,rb,lb")
key("q,w,e,r,t,y,etc")

All the buttons work through joystick emulation, with off being 0.0 and on 1.0. leftx and y are also w,a,s,d on the keyboard, rightx and y are the arrow buttons.

I think technically this is the final version. SP3 X is actually separate, since models made with it probably won't work in SPIV.

I dunno; I think that cone's watching me...

Scripting is kind of up to you; what you want is to end up with a value, which is what the joint/thruster/emitter/magnet/whatever will be set to. Scripts run each frame of the simulation, so if something changes, like an input from a joystick, then the script will update using this new input. The codes do logical calculations, putting them together, changing them and making them do what you want is up to you; a basic understanding of algebra will help. Search through the forums for the specifics, but there are 'if' functions, which do a test and give a value for either true or false. 'if, elsif' functions do a new test if the first one was false. There is a script that will cycle through values based on the frame number, and there are little snippets which do nice, easy to understand stuff like '0.5-lefty', which, on a motor, allows reversable control using lefty, which is w,s or the left joystick's up/down.

Ah we both had it too, but I think we both reinstalled it No worries, SP3 X is just a few days away...

I think on touch and tick have been removed in this release, or hidden anyway. People with the first download of SP3RC1 might still have it showing

Ooh... oooooohhhhhhh! So this is the collision detection.....

I'm not totally sure what you're trying to achieve there; the code is pretty specific to my particular vehicle. Also note that I had to take into account that joyRY is the wrong way round for driving use; the left trigger increases the value, while the right trigger decreases it.

Yay! Very fun. Thanks for bringing back no collision state, it fixed a big problem I was having.

Whoa, slow down. The blue fields are the ones that can use code...

Sure...

Thruster:

if(joyRY<0.3);a*2000;else;0;end

Emitter (flame effect):

if(joyRY<0.3);a*1;else;0;end

Rate and lifetime are both set to 1.

Motors:

if(joyRY>0.5);-0.2;elsif(joyRY<0.3);0.5-joyRY+a;else;0.5-joyRY;end

This is for slow reverse. The boost here is really just a relic from an old test.

It's an if function, so if the accelerator is pressed a certain amount, then the force is a*2000, otherwise just 0.

You should know Hobbnob, you're the only person that's rated the first version

Latest version of MotorSketch uses textures and grass sprites. Result is a good looking but still playable game; and thanks to the no collision state I've been able to keep the boost flame effect. I'm very happy with the camera rig, which can be rotated around the car and is springy, absorbing impacts and playing much more like a conventional game. Still alot of work to be done, especially on optimizing the file size... this is maybe half way through, but it's already topping off 9MB (This is reduced from an insane 15MB!). Textures need to be tiled properly and compressed, then used at a smaller scale on surfaces, but here is how it looks so far:

I think... I THINK that sound is only supported as an event, so no really fancy stuff with collisions. I guess on touch and click are event based script windows; rate could be how often they're excecuted. Till there's a proper post, it's all guesswork.... as far as I can tell, variables are still lost after every frame, and I'm not sure about global variable support.

So do I, it's released but I guess Chris hasn't finished the post about it.
I removed link when I saw Hobbnobs's! http://code.google.com/p/sketchyphysics2/downloads/detail?name=SetupSketchyPhysics3RC1-WinInstaller.exe&can=1&q=

True. I think the setting, which may or may not come in a later release, will just be individual density settings for each object, not specific weight settings.

Experimental... now I'm curious...