5 ms·
It moves differently in different browsers for me. And neither instance seems to actually make physical sense. In Chrome, the fourth box from the top starts sl
by FroshKiller 9y ago
It moves differently in different browsers for me. And neither instance seems to actually make physical sense.
In Chrome, the fourth box from the top starts sliding when it hits the floor, pushing the box to the right clear off the floor box. Every box eventually slides along the floor and falls into the pit.
In Firefox, the fourth from the top stays put. It never pushes the box on the right, though all the rest eventually slide into the pit.
- SketchySeaBeast 9y agoIn Firefox Developer Edition everything happens faster than in regular Firefox, though they seem to end at the same result. I wonder why that is. Animation doesn't seem much faster. I think the "neither instance seems to actually make physical sense" is due to a lack of friction.
- xchip 9y agoThe animation speed is determined by a timer, this should make it run the same in all the browsers. Is the simulation nice and smooth all the time? Friction is a biggie that I need to add ASAP!
- pjc50 9y agoI suspect you're experiencing the joy of floating-point nondeterminism. Edit: yup, it's the same every time per browser, but I can have e.g. Edge and Chrome running next to one another doing different things.
- archgoon 9y agoHey hey hey, let's not blame floating point here ;). Floating point is completely deterministic (as you note by getting the same behavior every time you run the simulation in the browser). I'm looking at the js spec, and there shouldn't be any freedom in evaluating floating point expressions (but overly clever browser vendors may have ignored that and reordered them anyhow). However, I do know for a fact that the implementations of the Math.sin and Math.cos functions are browser specific, https://tc39.github.io/ecma262/#sec-math.sin https://tc39.github.io/ecma262/#sec-math.sin so that alone will remove any chance at browser independent reproducibility, without additional controls. Be interesting to see if replacing Math.cos and Math.sin with your own implementation would remove the cross browser dependency. Btw, spec conforming implementation of Math.sin function sin(x) { if ( x === Infinity || x === -Infinity || x === NaN) { return NaN; } return x; }
- xchip 9y agothat is quite strange... the time step is always the same no matter on how the frames are rendered.... the animation should be identical
- potench 9y agotry using requestAnimationFrame instead of a timer
- xchip 9y agoAwesome, I didnt know about that one (still learning!), thanks!
- dkonofalski 9y agoFor me, boxes move underneath other boxes due to the lack of friction. It's the exact same movement every time. I wonder why I'm getting downvoted.