Video wird geladen...
Video konnte nicht geladen werden
Opus 5 + Three.js performance is insane. You vs. 100,000+ bugs w/ real ragdoll physics. Link to play below ⬇️
27,871 Aufrufe • vor 1 Monat •via X (Twitter)
13 Kommentare

Default setting will automatically adjust resolution, number of bugs, etc. to maximize frames per second. You can tweak them based on your system. I got as many as ~130K bugs on screen at once on my mac studio. 🤯

It's freezing for me. Can't even move, but it's showing something. My CPU is spiking and my GPU is not being used. I'm on Chrome/Windows, default settings on the browser.

looks like a compile issue with the WebGPU shaders in chrome on windows. i'll push a fix for it.

This is really insane Michael, did you host(URL) somewhere or code pushed to git?

URL here!

Literally me when my son leaves a piece of banana on the kitchen floor overnight in the summer.

🤣

which physics engine? I'm digging box3d in wasm

rapier 3D in wasm. it handles the player, arena collisions, and physical bug pile. the huge living swarm is custom GPU compute rather than 100k rapier bodies. wasm physics is great for browser games!

interesting. not seeing any wasm in the network tab in chrome dev tools.

good catch, I'm using dimforge rapier3d-compat. The compat build embeds the WASM binary as base64 inside the rapier js chunk. so chrome won’t show a separate wasm request it just appears as the large rapier js file instead.

Incredible. Quite impressive

"visiting asmongold's home" simulator
