Algodoo

If I were you, I'd have waited a little more before uploading it. It's insanely huge, so the empty shells float like they're on the moon, the ejection makes the shell go forward and sometimes get caught between the barrel and the bolt, and the trigger hasn't got way to move. It lacks burst and auto (i dunno about burst, but auto is easy to do with a disconnector) and the mag is not removable. although I don't care much about that one

But ihe bolt lock is brand new and good and I haven't seen any famas here. I hope you get it done!

I'm not rating right now because i wanna see the last version. I'd put it a 7 right now but I won't be able to rate later if I do.

P.S Why do you comment "10/10" on scenes but never actually rate?

The bump is not rendered because the polygon is too big. You should cut it in 30 meter parts. Also try using 100 Hz (Options => Simulation and change the slider)

What's your native language? I speak Spanish (argentinian). If you don't understand something, tell me!

Awesome scene. Sometimes it bugs and disintegrates but that is made by the springs, and I'm not sure if there's a solution to that

Hmm, I think you're not getting it. Xray also did a troll scene about marble races because we all hate them

Go to the script menu, go to the size var, and change it for anything smaller. This scene is totally useless. also, why would you want to make the smallest object possible here?

Doublefs, you can rate going to the same page but on any browser (Firefox, Chrome, or whatever: just copy the URL and ya), going below the scene info, and rating with the blue bar. You can't change the rating after you rated!

Weird, it doesn't explode for me. I finished the entire track and shifted perfectly to 4th gear.
If it's still exploding for you, you should be able to fix it if you put legacyMode 0 on the flywheel axle.

Bad thing is you're a noob too, and you're making a scene "to help newbies".
Also Why Do You Write Like This?

You should say, "This is my attempt" or something, 'cause I've seen 3 more here. But it's the best

There's an i12 car somewhere, but I can't remember the name

Whoa whoa whoa stop commenting so much You could have told us all that in one simple comment and with caps in the proper places ( )
So let's start:

1- Shaky things
This may happen if you have two objects in the same collision layer, i.e. they are upon each other and that wouldn't be possible in real life at all. Just uncheck their collision layer.
OR go to Options -> Simulation -> frequency slider and raise it to 120 or 200 Hz. that makes the scene more accurate but keep in mind that it's gonna lag if you use lots of water or 100+ objects

2- Spongify crashes game
There's no solution to that in short term, because the developers are not working on Algodoo anymore (maybe later they'll do something, but not right now.) Anyways no one uses that feature.

3- No comments
Make better scenes

4- Grinders crash the game
Nope, that's your computer. Also those "grinders" (aka laser cutters) cut the pieces to a very small size, and then cut it again if they're still there. So that gives insane amounts of lag. Just try not to use it.

5- People are gonna quit Algodoo
Most of us did, temporarily. I went AWOL for 'bout 3 months or even more, because of lack of ideas even though I know some Thyme. Vaidas369 was absent even more time. But Algodoo isn't so freaking old (10 years?? xD) This version (2.1.0) has been around for less than 2 years, and some people who aren't active and uploading are still lurking around in Algobox and the forum.

6- NO SOUND
That's relative. There's no sound ingame and easy to use whatsoever, but you can add sound to Algodoo with a mod. But it's ridiculously hard to use as you need sound files and they are just played when you want them to be.
Also, think about it. If Algodoo had built-in sound and maybe some way to create your own sound file, why do you think it would be easy to use? Sound is hard to work with. P.P.S: this is a physics simulator, it isn't "just a normal 2015 game". It simulates physics, not sound

Thank God there's no word limit!

Thanks squirl! You haven't done many rotary engines though
GTMasterMan: You can also put hingeConstant 1e-30 (which is the minimum value or almost it) and you'll have a stretched axle. Then use brake or bend (bend is better than brake for engine camshafts, 'cause if you use brake the cams will unsync regardless of the torque you use, even if you use +inf)
pnvv: Nope, it doesn't do anything. It IS a turbo (it has a turbine ) but it's there because I wanted it to have a turbo. Also your engine was weaker maybe because this one has gun tech

I never said I wanted it to work xd

Perfect suspension and very good engine! But you should try to fix this

"This gun might not work well on slower computers"
I'm getting 60% sim time unless I delete the second mag, and i'm on decent hardware. Maybe you can try spawning a mag?
It looks damn awesome anyways. I tried doing the same with my Glock but it was even more unrealistic

Damn i7s. I've got an fx6300 at 4 GHz, 4 miserable gigs at 1333 MHz and an r9 280 (but videocards don't do anything here, my integrated hd3000 pulled out 60 FPS too!)

God oh God why!?!
Anyways that won't be uploaded for a long while. it runs at like 60º from the floor

dat v

You know it's not a v!

dat hyperrealisticness

Use my wankel's smoke if you want

It's balancing around, and the cycle is too big. Use only one beam to connect the dark yellow beam to the circle, and make the cycle smaller

Awesome!
Another way of doing this is putting a box with inertiaMultiplier +inf, and hinging it with bend or springs. If you fix it the monocycle wouldn't rotate at all

vaidas, you should read the description first!

But yeah, if you want the engine not to vibrate, you should make underpowered 2cyls

I thought no one else here knew Joerg. I've been following him for quite a lot of time too

P.S the scene is very good! Try making the starter chain even more dense if you want. It popped out nof its rail like 3 times for me

Huh. My engine has 0.8x0.9 m, weights 180 kg, and has 16 pistons. Is it usable?

I don't know why you said that you need to use spaces before and after an = , as Algodoo does that automatically; and that you need to use capital letters too, because the compiler doesn't need them. Besides it seems you don't use capital letters, at least for the text
Also, you should explain more that thing of the semicolon, because I believe it isn't right, and you should add IF clauses and scene.variables. Also mind that if you use onLaserHit and you want to change a property of a geometry (box, circle, or whatever) you have to use e.geom, for example e.geom.density = 0.

Only because of 0.05m?

Joke, I already cut it!
I was just testing you although it was partly true

Dang. Mine does 400 secs topping at 70 m/s! Your track is rough enough to make me brake (xD I never use brakes)