Algodoo

Ps, Algobox wasn't coded by Algoryx, it was created by Link0007, an old Algodoo admin who's practically been around since the beginning, gotta love how much work he put into this site.

Powered by a hinge!

I think you need to refine this a bit more.

From what I can see, you're not firing at the most optimum time, you should fire the fuel just as it's entering a downward stroke, boosting the speed of the moving piston.

I would suggest running your competitions description on the forums, as long as you follow the guidelines, you're safe.

Sorry, not been able to reply due to networking issues, should be fixed within the next 3 weeks, I hope...

But, I think the issue is caused by your rods, open the visulasation winodow (the toolbar on the right of the screen, botton icon), and select view forces, and also select to see total forces.

I believe that the hinges are somewhat out of place, causing random stress on the axels, causing weird forces as it tries to snap back into position. I think that these stresses somehow manage to cause what is shown as the total force, which as you may have noticed, manages to throw it around in a circle.

The button is simple

onClick()
(e)=>{
Scene.my.running = ! Scene.my.running
}
The ! is the operator for inverting a bool, so pressing it inverts the state (true/false) of the variable, and saves it back to itself.

(e)=>{
scene.my.running ? {
text = " RUNNING";
} : {
text = " PAUSED";
}
}

Then, this is a snip from the button too, (on postStep() ). We then us an if script in the thyme code to read the value, and perform the required code for the script to work.

In algodoo, onClick() will not work unless the scene is running, so you can't use it to unpause the scene itself, we are just using to to stop certian parts of code running so that other interactions can occur.

Essentially our code will be like:

(e)=>{
scene.my.running ? {
//do something, eval code, etc, etc
} : { //do nothing }
}

I think the best way to do this would be to take a look at one of kilinich's scenes where he uses an object to respawn the object with a new surface, and instead drop small blocks onto the object. I can't see the code being overly complex to modify, but I would need to take a look.

He's seen the issues of having a partner and the agreement to help each other no matter what! He's only still in the agreement because she knows where all the sharp knifes are! lol

Invisible springs.

k-wing can be found on Kilinich's algobox profile

Chains are glued to the background, and the impulse break limit on the axles of the main vehicle has a impulse break limit which causes the hinges to be removed.

Algobox only extracts the .phz file, however due to the limits of PHP as well as a few limitations of algodoo itself, there may be issues with algobox uploads over a certain file size limit.
This is a known limitation of algobox, please create an account onto the forums and upload the file on there, this will allow us to look into the situation.

Just have a quick clear of your cache and see if that improves the situation, or try another browser, I doubt it will work but it wouldn't be the first time it actually has.

Algobox also checks the md5 sums of the uploaded files (.phz is just a zip with the scene.phn and textures, with an md5 sums file) for the protection the system and algobox.

1st gear is a bit bumpy! but nice, 5/5!

Buildman, create a post on the forums, you can do this by clicking the registration link on the forums website and creating a new account. Please ask your questions in the relevant sections on there.

Seams to be broken in 2.1.0!

2.1.0, running in wine however I doubt that has anything to do with it. The engine doesn't seam to stay running, if I hold X till it gets too 10-11 (highest it will go from the starter), pressing the accel is the only way to keep it running slowly, clutch held down and clutch not held down, doesn't seam to make much of a difference.

Tops at around 140ish, nice vehicle! I just wish my PC had better drivers, (older ATI card and linux...)

But flipping great, 5/5!

Not bad, however it needs some work!

These are the 3 I can remember,
1. It's possible to have the fuel counter still going down, even when you've managed to stall/kill the engine
2. would be awesome if the revs slightly affected the fuel counter
3. fueling can be hard, you have to hold it just slightly away from the end, otherwise the laser doesn't hit the target.

I'd suggest patching it up and spending a few more hours on it and see what you can do, then re-upload it as a new scene

Yep, the car works perfectly fine, other than that refueling is a bit of a pain to get in the right place at first.

You might also want to mention that refueling and oiling is gradual, and not a quick 2 second point the laser in the correct place and go sorta thing

Deleted the bad vote on this scene, the user seems to have voted 2 reasonable scenes of yours low which have a sort of competition against his, which gives me the suspicion he is abusing the vote system, especially as he has refused to comment or even reply to a message. If it happens again, just report your own scene and I can easily take a quick look into it!

Issue should of been resolved.

The tooltips was disabled when the website was updated due to this issue, however it's not an issue on several other browsers, so it was missed by Algoryx when they was testing it for rolling it back out after a user requested it.

You know, I think that with a bit of maths it wouldn't be too hard to start spawning objects automatically.

You could have the laser run something such as:

if (tripped = false) {
tripped = true;
create_next(e.pos(0))
}

and have a function which spawns in the next obstacle.

And I think that the little birdy is a bit too heavy, he seams to drop a little too fast. Maybe tune the jump and dive rates a little.

You're welcome!
And, I feel strangely evil, probably for about a week

http://www.algodoo.com/fo … mp;t=10693

Reaaaaally hates entering first from neutral! But nice!

1188

AMD HD5450
Intel E5500

Guess it could be a whole lot worse!

Max memory limit is actually 2GB for a 32 bit application. And, like most applications, algodoo will run slower when it's left open for a while than when it's first open. I mainly attribute this to garbage memory collection, which in all honesty sucks in most games!

^ piston movement seems really unoptimised, waaaaaay too many moving parts, algodoo doesn't cope well with forces like those in a engine, I doubt you'll get much out of this.

Make them low powered, or use the arrows to turn a small wheel upon which the thruster is mounted, using a spring to make it return to normal position, use the arrow keys to rotate the circle.

As admins, we can send warnings to users. If you wish to message an admin, or communicate to others via PM, please register on the forums. It's what they're there for.

Hello!
We have a wonderful set of forums which you can access by clicking on the link at the top of the page, its a much nicer method to communicate on, allowing features such as Private Messages as well as allowing for a central place for everyone to communicate! ^^

Yeah, Potentially cool but the direct solver issues destroy the scene for me!