deleted
replyInteresting! It's stable on my machine. I wonder if this is due to floating-point differences.
replyOn my machine, the initial state isn't simulated. It only begins simulation when I touch it. At which point, the weight causes the bottom blocks to intersect each other significantly.
replyFor me, bottom blocks stay still while those on the very top fall down.
replyIf I open it, click on the background to activate the physics and just keep the tab open, pretty much all of the blocks that can collapse do eventually collapse.
replyThe Nebraska guy’s block remains surprisingly stable, even when the whole thing above it collapses. Very symbolic.
replyOne more pedantic nitpick: when a block gets wedged between two blocks at an angle, it gets slowly pushed out, although there is a lot of weight resting on the top block. That would be realistic only (maybe) if the blocks were made of ice, but not for other materials...
replyCoefficient of friction is way too low.
replyAnother reason not to let ice on the internet.
replyMaybe that's what I'm seeing.
replyI‘m guessing it‘s somewhat framerate-dependent.
replyThat's the javascript effect.
replyNah that's just the effect of turning on the simulation. The initial version isn't the same as the first steps because there's no weight. If you look closely after you click the blocks overlap slightly.
replySomething similar happens all the time in games when you go from a static version of something to the higher level of detail version with physics enabled, if the transition isn't handled gracefully or early enough you can get snapping.
Just like real life. Sit still, touch nothing, and watch everything fall apart all on its own ¯\_(ツ)_/¯
reply