Awesome
This is something I always said to Vaidas, he used overpowered engines in whatever he did, and that was a little bit annoying sometimes. Now here you used an engine with the right amunt of torque
Damn Germans that's "rather" overcomplicated for a trigger group. Anything new on your design?
P.S: I'd like to see your gunpowder rifle on Algobox just so that I can compare it to my approach
P.P.S This was under 3 pages of crap at the moment I saw it. now it SHOULD be on the popular tab
This one's very good! (But I always find ways to improve things here )
Just try this:
add a little bit more way to the bolt (0.4 m would be just fine) and put restitution to the part that limits the backwards movement of the bolt and to the bolt (I use 1.0 restitution on the two if the construction is sturdy enough, otherwise you can try 0.5 or less). that will increase your fire rate, and if you manage to chamber the round 0.3 or 0.4 meters less, it will work even better!
I always think like that because that's what I try to do here: guns with higher fire rate and low frequency, and, if possible, close-to-reality mechs
Our problem with marble races is that you actually spam them, so our scenes last less than half a day on the New tab. You don't have any control over how many scenes you upload!
IF you tried to upload less scenes per day (one or two) we'd all stop complaining. but there are certain users that upload like 10 scenes containing just colored polygon stickmen.
Our problem with marble races is that you actually spam them, so our scenes last less than half a day on the New tab. You don't have any control over how many scenes you upload!
IF you tried to upload less scenes per day (one or two) we'd all stop complaining. but there are certain users that upload like 10 scenes containing just colored polygon stickmen.
No, your scenes are very simple too! When we say "creative", we mean TAKE YOUR TIME to do a scene that (idk) solves a problem or does something but that has NOT been done 1090 times before! (search "algicosathlon")
Now the main problem we have is that you upload lots of scenes per day! If you limited the amount of scenes you upload to 1 or 2 scenes per day (which is a lot anyways) then this would be solved and we'd shut up.
Believe me, we talked about a scene limit in the forums (FOR EVERYONE), but some were opposed to it. I still think it'd be the only solution!
The main problem is that your timing AND ball despawn is messed up!
You should use stretched axles as transmissions (you put one, then drag one of the objects, then put
hingeConstant = 1e-30
and then put
bend = true
bendConstant = +inf
bendTarget = 0 (or whatever to make the ignition fire at just the right time)).
That will give you a lot of awesomeness! Also you should forget about that timeToLive thing and use a killer box well below where the ball spawns. when it goes down, it gets killed.
And remember that more density means better collisions! So you should leave the balls' radius at 0.5 meters, and change the density instead (from 1 or less to 500 or more).
You should make the piston longer or just a square because it will turn if you accelerate it too much. and you shouldn't use a counterweight, because axles are a copy of real life bearings, but they work rather elastically, and the counterweight will make vibrations only. also you won't need it at all as you have a starter.
And last but not least, use LOTS of DENSITY for the important objects! More density = more accuracy in sim!
Don't be dumb, I wasn't talking about you. your scenes are well above most algotriacontathlocosathialgodooers or kiddos or however you wanna call 'em
Also, just making a question: how old do you think I am?
That's much better! Now the problem is compression. you should move the cylinder lid (or however it's called ) 0.03125m lower, so that the ball gets squeezed between the piston and the cylinder once it's spawned. Also, use density as the accelerator! Leave radius at its maximum value, and change density to accelerate!
You should use this script:
density := (Keys.isDown("up")? 500:10);
radius:= 0.0625
then you can vary the values to make it faster at accelerating (change the 500) or slower at idle (change the 10)
Look at my engines if you want, especially at the scripts I use. they may seem complex, but after some time you'll get the basics of Thyme figured out! (assuming that you haven't already)
RAMTurtle, just post LESS SCENES PER DAY!
I don't care how you do that; you can merge scenes and post one each 6 hours, but don't post 150 per day! Algobox is being clogged up with crappy 2 KiB scenes!
Well, I did a server long ago with my olde pentium4. IF this gets worse it'd be time for Algo2!
Also, I think this "employee" is somehow wrong because we started doing better scenes in half a year or so (maybe more in my case ). but with Algodoo at a cost this was much better managed
The main problem we have is that you upload lots of scenes per day! If you limited the amount of scenes you upload to 1 or 2 scenes per day (which is a lot anyways) then this would be solved and we'd shut up.
Believe me, we talked about a scene limit in the forums (FOR EVERYONE), but some were opposed to it. I still think it'd be the only solution!
I think that the best solution would be implementing the "CATEGORY" in the integrated uploader/browser, and making it necessary to be able to upload a scene (like the title and description). Then, there should be an option to filter scenes (like checkboxes for each type...?)
Also it'd be nice to have a search option in the integrated browser. It's a little bit of a headache as it is now (having to copy the URL and rating from another browser)