lethalsquirl: Yes, the front wheel sometimes bury into the ground a bit and gets out, and if you accelerate much without any gear the engine explodes. And the tachometer isn't failing for me, maybe I'll revise it later. What Algodoo version are you using? The angVel reader script is only for 2.0.2 b15.
Anyways, thanks! I'll try to make it better.
Kilinich: when you accelerate in neutral? I'll change the legacyMode to the engine, but he first 3 gears of the transmission have legacyMode 1 because they spin slowly, and they have to do most strenght. I'll see that as soon as I can.
Yes, all is on the polygons. The cams collision doesn't change as much, I tested it and it's the same. I dropped on that design just because it was the same at collision terms.
And the valves, those crappy valves were rectangles first, but then I cutted them to make them close completely.
I'll change all that tomorrow. Thanks, Gent. And you're right, we all learn from each other here (especially from Kilinich ).
Yep, I tried to put it in a old passat. I couldn't. My first strong engine was this one, it was bad timed, but worked. It has virtually infinite strenght and speed.
P.S.: Your engine's timing is a bit bad, lasers aren't the best for this. Put more lasers at different angles (like at 5°) and it should work faster!
Yes, the little circles on the timing of your engines started to fail in the 1.9.9.9b (lol emil!). They were awesome, for example Lara Croft's motorcycle.
Also I was looking at the 2.0.2 topic at the forums and found this:
" * IMP: Improved collision detection between polygons with circular outer shell vs polygons and circles. A circle and a circular polygon should now behave equally in all situations. "
So the cams work equally? (I'll need a lawyer to make you accept the cams)
Oh, the memory leak. The whole scene has erased, and when I press play, the screen turns white (all the pixels) and then it runs out of memory (I have 2 GB), then the writing error, and Algodoo closes. EMIL, DO SOMETHING!
No. Maybe they'll listen algobot... lol.
When hinges didn't stretch, i made a stupid automatic spring stretcher. It worked hell bad, it was to connect a piston and crankshaft to make kind of a thruster nonscripted thingy. Didn't work as expected, so now it may be in the dark corners of my hard disk !
This software isn't perfect for education. The air friction is not a mysterious force that brakes objects, nor the thrusters exist in real world. And objects haven't got infinite strenght and no elasticity. But the strangest things are the hinges, you can stretch them, and give them a motor that works with no fuel? Yes, the gui was the big change between .8.5 and .9, but it wasn't so important. I use the same toolbars layout as the 1.8.5! It's more comfortable for me.
Anyways, guys, you should work more on the physics. Like the collisions for example, now that you have the gui perfected for selling .
P.S: we need a :trollface: as well as an algobox5000.
The timing works like this: when the engime goes slow (20 rad/s) the circles touch the center circle and they make friction. Then the spawner gets down and it powers the engine until it gets to 40 rad's. This repeats all the time to power it.
This is crap, right? Just try to make something good, not 100 kiB scenes that have 6 geoms and 8 springs. And vaidas, you didn't invent this. Every algodooer and phunner has built this.
Sorry, I didnt want to be so mean with you, but just think that you've uploaded like ten scenes like this today. If you follow like that, you will get scene 10000...
Sorry for bad spelling, TouchPal is a bit hard to use.