Nice donut in the demo, but would love to see a human model for a more fun demo :) Ideally with a proper weight map for the different body parts too, seems well done enough that you could get really close to something realistic.
Nice to see someone else doing physics in the browser. And this looks well put together, keeping the engine dependency free and separate from the renderer is a good call, that is what makes it easy to reuse in Three or Babylon.
One question: how does it hold up when the framerate changes? Spring jiggle like this usually either blows up or feels different when the timestep moves around. Are you using a fixed timestep, or just relying on the damping to keep it stable?
The accumulator pattern keeps simulations stable in the face of variable frame rate. Accumulate the frame dt into an accum variable. If accum>fixed_physics_dt then step_physics until false. I'm assuming the author did something like that because it's standard practise.
Why would the physics timestep move around? Typically you keep that fixed and separate, especially not locked to the display framerate, physics get really wonky then regardless of what you do.
Advancing the human race forward.
Nice donut in the demo, but would love to see a human model for a more fun demo :) Ideally with a proper weight map for the different body parts too, seems well done enough that you could get really close to something realistic.
That's probably the intent given the link in their github bio
Could be used for soft sea fish models
Nice to see someone else doing physics in the browser. And this looks well put together, keeping the engine dependency free and separate from the renderer is a good call, that is what makes it easy to reuse in Three or Babylon.
One question: how does it hold up when the framerate changes? Spring jiggle like this usually either blows up or feels different when the timestep moves around. Are you using a fixed timestep, or just relying on the damping to keep it stable?
The accumulator pattern keeps simulations stable in the face of variable frame rate. Accumulate the frame dt into an accum variable. If accum>fixed_physics_dt then step_physics until false. I'm assuming the author did something like that because it's standard practise.
https://www.gafferongames.com/post/fix_your_timestep/
> when the timestep moves around
Why would the physics timestep move around? Typically you keep that fixed and separate, especially not locked to the display framerate, physics get really wonky then regardless of what you do.
I had vastly different expectations, though I suppose this could lead to them..