Which is the current wiki please?

I might try and do an fps rig. it will probably end up keyboard control cos i don't have a gamepad though. I thought of a way of making one sprint though with a variation of the scripted transmission jake on the warehouse made.

There are several methods of controlling the camera. In that video he started the simulation and then right clicked the torso and set the camera to follow.

You can also setup a Scene and put a certain description to get the same results. In that case you can disable camera control by changing the scene page before you start the simulation. Or delete it if need be.

Thanks for these 😄

Well I did not succeed... I attached the model for you geniuses. I would be very happy if anyone would give it a try 😄

rubik_crash010.skp.zip

I spent about 2hrs pouring over the code looking for what changed before I tried it in SP2 and found the bug was in that version too. Its servos that work ok with the values reversed.

I could fix it pretty easy. But if I do it will break any existing models that happen to depend on that behavior.

Did this in a few hours. It uses the Knight model and animation from Scott Lininger's Prince IO game:
http://www.sketchucation.com/forums/scf/viewtopic.php?f=180&t=14291&start=0&st=0&sk=t&sd=a

It uses lookAt to point the knight in the direction the joystick is pointed. and the new push command to make him move.

The animation is a trick used in the Knight game. The object really contains all the animations as hidden geometry. I cheated a little bit on the animation playback. 😄

The original idea was that the joints are atomic and can be joined to do what you want. Just connect 3 Springs and you have the same result as a specialized 3DSpring.

The problem is the "just". Its a pain to connect up 3 joints. Not to mention not simple to envision what the result will be.

SPIV will fix the pain to connect part. But a 3d spring may be possible in SP3x. Maybe a desiredPosition property on objects or something.

Hi CPhillips
Ok, thanks for the feedback. I noticed this feature, but didn't know its use. I'll look at this, soon.

MALAISE 😄

I dont know to be honest with you. Its probably newtons or some fraction of a newton.

Mmmm. fig newtons...

All of the above reasons are good. Plus you can give feedback and contribute to the design of SPIV.

One other variable function is

It can be a useful shortcut.

Either will work. I will edit this into the Faq post.

Thanks Alienizer!

Pretty cool! No idea how you did it. Yet...😄

I think it might be behaving differently than in 2.0. Can anyone confirm that it does the same thing. I dont have a good copy of 2.0 at the moment.

Of course, as said before, Thank you very much for taking YOUR time getting it done.

Keep up the good work! 😉

why bother with gmail chat and msn? just keep on using this thread. 😄

Never mind, I figured it out. I had to group the motors with the main object.

Yes. The video is for the next version. It is called SP3x (for experimental) and will probably be out in a few days.

The reason for 2 versions is that models that use OnTouch and OnTick might not work in future releases.

I am not planning on restricting 3dwarehouse. But I want to make it clear that these models are much more likely to break in the future.

I am really happy that most 2.0 models still work in 3.0 and I want to try to keep that going.

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.