Webphysics Live Demo: https://jure.github.io/webphysics/
Code: https://github.com/jure/webphysics
#The #WebGPU AVBD-based physics engine is now live!
torn salmon
finite atlas
Interesting, but is slow 😖
i test on window chrome
I think there's something blocking
maybe look this
https://github.com/holtsetio/softbodies
too optimize
torn salmon
what are your specs? and which example? I’ve been gunning for stability first, but there are numerous optimizations possible, so do point out what is slow for you. Browser compatibility is also in the queue
for reference, most of the examples run 120 fps on my m3 max, with the exception of behemoths such as 64k blocks, or the coliseum
torn salmon
Some discussion starting on the hackernews front page now, if anyone wants to jump in
knotty fable
You might not know this,but i actually saw your work in graphics programming group and was inspired to try running some of my own physics experiments over webgpu,my works went on very different directions.But still its coolv. Bv,although mine is rather my own renderer,so theres that maybe you might find interesting https://null-graph.web.app/
https://youtu.be/Pku1u5erGrc?si=OKy1c8RD0G_4IAv7
torn salmon
very trippy examples! 🙂
elfin ferry
it works smoothly on my machine
tho seems like on Firefox / zen it cannot get FPS nor cpu / gpu stats
torn salmon
it’s not supposed to work on Firefox at all! 🙂 I have to check if ptr function arguments are now possible, that would be very neat
finite atlas
i'm on windows chrome / threadripper 32 core / rtx 4090
first simple block demo run 20 fps ! but sometime more is unstable
40 % gpu is a lot for so simple graphics
torn salmon
anything in the logs? something has definitely gone wrong there
@lth turning on the 'debug behavior' toggle, will slow things down by quite a lot, so make sure that isn't enabled. Also, if you could, enable 'debug timing' and paste the output for one frame in the console here, I'm very interested in seeing where the bulk of that time/frame goes
finite atlas
there's already a bunch of logs
haa seam's much better without debug timing
is enable by default
yea is debug timing the problem's
amber estuary
The deafult 5x5x5 stack is slow for me in latest Safari on Mac M1 Pro, getting around 10 FPS without any debug timings
Smooth in Chrome
amber estuary
It is keeping the GPU compute maxed out in Safari for some reason, I think (unlike WebGL) Safari has a different backend from Chrome for WebGPU?
torn salmon
looks like ‘debug behavior’ toggle is enabled?
oh, sorry, yall went past that already, Discord acting up 🙂
cross browser support is in the queue, I’m surprised it even works in safari and firefox at all (ptr args, subgroup support) contributions welcome!
knotty fable
It is keeping the GPU compute maxed out in Safari for some reason, I think (unli...
You would see half the frame rates in safari compared to chrome a freind told me
amber estuary
Chrome was hitting 60 FPS but the GPU was still at maximum perf state and close to maxed out. Perhaps some of the techniques just don't map that well to Metal?
amber estuary
You would see half the frame rates in safari compared to chrome a freind told me
Hard to make such sweeping generalizations if the backends are different. For WebGL both Chrome and Safari use ANGLE to translate to Metal so perf tends to be similar