@chriswman said:

Thanx for the reply but sketchup crashes everytime I try to "play".

Does anyone else have a problem with that model crashing? It seems to work OK on my PC. To ChrisWMan: Is it just my model crashing or are you generally having a problem with SP crashing?

I have attached a new file with examples of joining hinges and sliders. In this one I have not directly connected the hinge to the slider in case that is what is causing your crashing problem. Let me know if this one works. The small white connecting blocks can be made invisible if required.

IndirectJoints.skp

Hi angy,

I'm afraid 'sand' might be too much for most computers to handle, so I have attached a model with a load of bricks that can be offloaded instead. I hope your son finds it inspirational and it spurs him on to greater things. Perhaps he might like to have a go at animating the wheels?

dump truck2b.skp

Yes, it is possible. Just group the hinge with the piston and then connect to the rest of the model. This works, but is not very rigid. (See the red group in the attached model file.) A better way is to put an intermediate block between the hinge and the piston, which gives a more rigid set up. (See the green group in the attached.) If the intermediate group spoils the visual look of the model it can be made invisible or made smaller. If making smaller, increase the density of the intermediate object to compensate and maintain the rigidity. For some applications you might actually prefer the more flexible result of the direct method.

DirectJoints.skp

Just for fun I have added some rudimentary suspension and steering control to your wheel assembly. Hope you find it useful.

FRONT WHEEL JOINT3.skp

Check out the attached file. I have scaled up the whole model except the physics joints by a factor of ten, made the white cylinders cylindrical rather than the default rectangular shape and made the wheel a sphere rather than convex hull. All the joints move freely now.

FRONT WHEEL JOINT2.skp

Hi jemaxwell,

If you you could upload a file with what you have so far it would be lot easier for us to pinpoint the problem.

Offhand it may be the small dimensions you are working with. Try building a similar model with everything scaled up by a factor of ten and see if that helps. Do your objects seem to be dominated by the size of the joints?

Kev.

Hi Angy and son,

Well your son made a good attempt and got everything lined up properly. He was just fell foul of the less intuitive aspects of using SketchyPhysics. I have attached a simplified and fixed windmill (windmill3) and another file (windmill2) to act as a tutorial for your son to practice on.

First thing I should mention is that the everything seems to have been made into one big group. Everything in a group moves as one and nothing in a group moves independently of other parts of the group and this is the main reason the windmill does not work.

Using windmill2 as the tutorial:

1. Select the big block and the two hinges and make them a group.
2. Click on the "UI" button and with the big block selected, tick the "static" box.
3. Select the 3 parts of the handle and make them a group. (Handle assembly)
4. Select the 4 rectangular blades and 2 cylinders and make them a group. (Fan assembly)
5. Select the handle and the fan assemblies and make them one group. (this makes them move together so need for a connecting axle through the block)
6. Click on the "Joint Connector Tool" (next to the "UI" button) and click on the big block.
7. Now holding "ctrl" (on the right of the keyboard) and with the big block still selected, click on the two hinges.
8. Press the spacebar or select the arrow pointer tool and click on the handle or fan. In the UI it should say connected to hinge4102 and hinge2418 if everything has been done right. The model should now be ready to run.

Some general rules:

If connecting two objects with a joint, the joint should be grouped with one of the objects and connected (using the joint connector tool) with the other object.

Parts that move independently should not be grouped together.

Use as few joints as possible. The original had 6 when 1 or 2 is sufficient.

Always group joints last as they do not work if grouped in lower layers.

Do not superimpose solids or separate groups on each other so that they share the same space. For example in the original model there was an axle passing right through the main block. This will cause problems. If you must do this, set one of the objects such as the axle to "no-collision" and "ignore" in the UI.

Hope that helps. Good luck!

windmill3.skp

windmill2.skp

@unknownuser said:

Well here is a quick and crude solution, it just checks if all the named blocks are positioned beyond the border.

Once again some really impressive ruby coding from Mr.K! I like the use of two gyros and cylinders for the corner squares. It all works so well!

Thanks for sharing this with us. I has a look at your mini game and I see there is a LOT I can learn from you. Your Ruby programming skills and knowledge of SketchyPhysics inner workings is just awesome.

About the game itself, bumping into your future/past self going about its/your business is mind bending, even more so than the well known "Portal" games. Hopefully you are not doing any damage to the fabric of time and what about the grandfather paradox?

Mr.K beat me to it!

My version has a gyro too, but I have added a hidden layer with chamfered corners which makes it less likely that the corners will catch on each other. You can pretty much "slam dunk" the pieces into place, but to be honest it not much improvement on Mr.K's version which is pretty good already.

slidergame_v03e.skp

@fransko said:

I want to make the game so that the block through the hole into a different level is
but I'm stuck

I have fixed the problem with your last file. Some code got deleted along with the box that was originally at the end of the level. I have also added some extra code to teleport the box to the new level when you reach the end of the old level. There are some extra green "short cut" tiles on the maze to make testing easier and they can always be easily deleted. I have also added some comments to the ruby coding to make it easier to understand for anyone who might be interested.

See attached, now with two levels!

bloxV10d.skp

This is like some sort of magic at work. Burn them!

@mike lucey said:

Anyway! the latest thing I have learned about bees is that they may be able to help up combat terrorism! Check out,

Bee venom used to create ultra-sensitive explosives sensor

http://www.gizmag.com/bee-venom-used-to-create-ultra-sensitive-explosives-sensor/18609/?utm_source=Gizmag+Subscribers&utm_campaign=c77a079881-UA-2235360-4&utm_medium=email

I thought you might be interested in this: http://forum.beemaster.com/index.php?topic=30478.0 Live bees can be trained to detect numerous substances such as drugs or explosives by feeding them sugar laced with the scent of the substance you are looking for. Apparently they are more effective than sniffer dogs!

Maybe you can post a screenshot of the problem you are having, because I am not sure I exactly understand the problem.

@unknownuser said:

You could add a timer so the box turns fully on every button press, that way it's far less likely to break the level.

I have now done that but movement was still a bit hit and miss so more was required. The latest version now includes the "idea" I mentioned in the earlier thread, to make the model more "rigid" but I had to learn a fair bit more about ruby scripting to actually implement the idea which involves using the teleport command. The model is now totally "rigid" with precise movement and hopefully it is impossible to break a level now (but someone always finds a way lol). The puzzle is now less about dexterity and more about puzzle solving.

Model now includes sounds.

You can make your own puzzle level by turning on on the "hiddenBoundary" layer. Then all you have to do is move or copy the white tiles to where the block is allowed to go, and the red tiles to where the block is not allowed to go.

Check it out!

bloxV09c.skp

Pilou, you are always finding the good stuff!

@unknownuser said:

Well I modified my SketchyReplay a while back so it can record camera, but it then always records the camera so keep your backup files close.

http://forums.sketchucation.com/viewtopic.php?f=61&t=36029#p317654

Hi Mr.K,

Tried your modified file and works fine for me, recording the camera movements. Nice work!

This is what works for me:

1. Start the physics simulation.
2. Toggle the red record button "down" to start recording.
3. Do the simulation / animation action stuff.
4. Toggle the red record button "up" to stop recording.
5. Stop the physics simulation.
6. It then asks if you want to save the animation. Click yes.
7. Click rewind to reset the camera to start position.
8. Save the model. (This is when the recording is really saved.) It is probably wise to save the model to a different name, because if the start of the recording is not the reset position of your model, it can ruin your carefully set up starting position.

The bad news is that the camera movements are not recorded. In the attached file, the camera was set to follow the block which it did during the recording, but the camera is static during the playback. Sorry about that.

Load the attached file and click on the "play animation" button to see a short recording of me cheating at the BLOX game discussed in another thread. (You usually have to click the button twice.)

@ace baker said:

Only, it never works that way. One problem, it keeps saying "requires Sketchyphysics 3.2". I look in my version number, and it says version 3.1. Except I thought I downloaded 3.2.

That is a known "bug". You have SP3.2 and the version number is reported incorrectly. SP 3.2 always puts "Requires SketchyPhysics3.2" in the watermark to let people know they require SP3.2 to run the model if they download it from the warehouse, so that is completely normal. Unfortunately it seems you cannot record camera movements, just as you cannot change scenes when the simulation is running. (Hopefully someone will prove me wrong.) Maybe in SP4.

I think the workaround is to use screen capture recording software and record what is on your screen, if you need to get the camera movements.

bloxV07 cam.skp

This is my latest version. I have fine tuned the model and simplified the mechanics a fair bit. There are now no joints in the model. It works fairly well and I have included a real "mini puzzle" level that puts a message on the screen, if you get to the box at the end.

To see how it works, enable the physics joints layer and turn off layer 3.

bloxV0.7.skp

I like the idea in principle, but I have not had an email after completing the registration, that will allow me to log in. I like that you are trying to do something constructive and helpful here perhaps with a social element.