Bouyancy fields should be possible soon but Chris says fluid simulation is, uh, right out of the water.

Woohoo! Works totally fine for me, have you tried reinstalling it? It resets the camera after the simulation, that's brilliant! But it doesn't remember the FOV setting

Ooooh and a frame counter... and no collision! Yes! What does on touch and on click do; are they proper script windows??

Hobbnob, it's release candidate one, so it's nearly ready for full release. Either this version will be fully announced, or there'll be one more version after this.

You can sort of make stuff heavier be increasing the bounding box's size without increasing the mesh's size.

Yeah, what are you talking about?? I can't find RC1 anywhere, did Chris send it to you??

8 so that 7 works properly with emitters.

I know; It may, however, be possible to disable normal shortcuts for the duration of the simulation.

Have a look at this thread, I posted a pretty thorough guide:
http://www.sketchucation.com/forums/scf/viewtopic.php?f=61&t=17539&start=0

Sorry, I know there have been way too many requests already, but I can't resist asking... here's everything I can think of, for SP3, SPIV and onwards:

SP3:

1. Variables that stay between frames
2. Global variables, that can be changed by any formula box to affect any other
3. Multi-line formula boxes (Maybe drop-down, to save space?)
4. Allow gyro to stop an object rotating (checkbox)
5. Damp settings for ball and universal joints
6. Allow the keyboard controls to work without the control panel being highlighted

SPIV:

1. Allow joint names to be used in script as controllers, with choice of the connected object... like 'hinge1992("box1")'
2. Bouyancy volumes/fields (can't remember the name)
3. Emit complex objects, like vehicles
4. Have camera objects which the camera will view from in the simulation, which can be chaged with scene (Camera camera1.) at authourtime or with script at runtime
5. All physics settings controlled from within the UI; when nothing is selected, the overall settings are displayed.
6. Buttons in the UI to increase/decrease joint settings values
7. Physics events, like certain objects colliding. Example: collision((target),bullet,shell,rocket) to trigger if bullet, shell or rocket hits target
8. Setting to change the entity name of an emitted object
9. Overall slider/settings for realism vs speed of simulation (like in the newton playground)
10. Names for magnets, so they only affect magnetic objects with the same name
11. Materials, with appropriate sound, friction and density settings (fully customizable)
12. Trigger sounds from within script
13. Full screen simulations (if possible)

The future:

1. An exporter that can export .exe files from the model, with a more effecient renderer than SU's
2. Destructable objects
3. Deformable objects/soft body physics
4. Cloth/rope simulation
5. 2,3 and 4 maybe with a new physics engine?? (Like PhysX)

When the technology is available:

1. Fluid simulation
2. Effects like explosions, dynamic lighting, glows, reflections etc etc (Again, maybe with a custom/freeware renderer?). This'd transform SP into a fully-fledged SU game maker!

I'm almost definately asking too much with the later stuff, but I hope some of this can be implemented. I don't want to sound like I don't appreciate the work you've already done, because seriously, you've done an awesome job... keep it up!

'rand' generates a random value bigger than 0 and smaller than 1. It'll refresh every frame, but there's no way at the moment to stop this; if it's too fast, I guess you could decrease the joint's accel, but there's not that much you can do from within the script. I'm not sure what you mean by 'explain the script'... can you go into more detail?

Very nice ... however

That uses the Nvidia PhysX engine; sketchyphysics uses Newton Game dynamics. Although the PhysX SDK is free, it's waaaay too late to change now... SPVI, perhaps?

Oooh, looks like we got us a bug! It doesn't make the slider! If you force sketchyphyics to make the slider using another box, it works... turn on the object's thruster setting, and use Chris' code, so that the thruster has no effect.
Wierd...

When you press UI, the inspector is SUPPOSED to come up; that's what the UI is, it's for setup of the simulation; the control panel with the sliders comes up when you start the simulation, by pressing play.

EDIT/ You do have the latest version, don't you? The first version didn't have a control panel. /EDIT

Whaddya mean, no way to fix it?!? oscillator(50/(-righty+1)) does the trick nicely

Good walker, shame about the joysticks

Not at the moment, emitted objects lose all settings applied to them, like connected joints, their state, thruster/magnet/magnetic settings, and whether they're hidden. Maybe a dialouge for choosing settings for emitted objects in SPIV? The nocollision state would be very useful for particle effects... and maybe the ability to gyro-stabilise them?

The problem with this is that it only works through the cones physically moving each other; what's really needed is a way to use sketchyphysics gears to do it, so the parts don't have to be touching.

Oh yeah! Sorry... I just grabbed one of the wheels, and it didn't stop, so it didn't look like it was working.

Sorry but I don't think that's it. If you hold one wheel still, the power should be sent to the other wheel.

WIP on my next car game... improved stability and handling since warehouse upload, also with more detail on the dune buggy and slow reverse 'gear'... but, along with mid-air control, the best feature by far is the thruster-powered hyper-boost!! It's powerful enough to give you serious air-time, and you can even, um, drive vertically...

Have fun!

leftx = steering
joyRY = throttle
a = Hyper-Boost
leftx/y = mid-air yaw/pitch

NOTE: Just the testing ground

Something like the magnet switches from LBP could achieve all kinds of stuff like this; they're basically proximity switches. If we were able to use entity names within script, something like "if(proximity(box1,box2)<500);1.0;else;0.0;end" would do it. The way I've written that is probably stupid, but you get the idea... expanding on this, you could have sketchyphysics know an object's position in relation to the origin, something like "x/y/zproximity(origin,box1)", its x/y/z speed and how much it's pitch/roll/yawing. Also use joint names in script, like "0.5-hinge1000", for levers etc. If it's possible, that'd be awesome, if it's not, never mind.