three-mesh-bvh VS polygonjs

the default one ( with the sop/boolean node ) uses https://github.com/gkjohnson/three-mesh-bvh, which is very stable already.

Have you tried using https://github.com/gkjohnson/three-mesh-bvh ? That may give you some easier collision detection tools.

The game is currently unplayable for me (10fps) and I can run Witcher 3, so I definitely should be able to run this. You need to do some heavy optimizations. Looking at the console, while there is a high amount of time spent on rendering, over half the frame is spent on raycasting. You have to either reduce the amount of raycasters in your game, reduce the number of objects raycast against, divide meshes into smaller chunks (default raycast loops through entire geometry, so highpoly large meshes are really bad for you) and/or use BVH to speed up raycasting https://github.com/gkjohnson/three-mesh-bvh

There is a different raycast method, not too hard to implement and that probably will run a lot better https://github.com/gkjohnson/three-mesh-bvh

or trying https://github.com/gkjohnson/three-mesh-bvh

That's the path I took with Polygonjs ( https://polygonjs.com ), and a game I've just released ( https://polyreplay.com/minesweepertwist ), with more coming shortly.

But it didn't start like that. It only started as a tool I could use to deliver client projects, as I was trying to become a freelance for interactive 3D scenes for the web.

Project after project ( some examples here: https://polygon-lab.com/ ), I could improve Polygonjs. Then I found clients who would be interested enough to buy licenses, and would give valuable feedback which would help the project grow even more.

And a few clients asking for not just interactive sites, but also games. This pushed Polygonjs further, and after several games released, it definitely qualifies as a game engine.

So this is generally an advice I give to people who want to become freelancers. Build a tool that solves a problem in your space, as this gives you an edge, and you'll also get the chance to confront that tool to reality, which will help it - and you - grow. This becomes a virtuous circle very quickly.

You can have a look how I do it in Polygonjs (which is a node-based design tool based on threejs), in this example scene.

If you're familiar with Houdini, I invite you to try Polygonjs, which is based on threejs and inspired by Houdini. You can basically build threejs in a procedural way, with just nodes.

You could try Polygonjs. It's inspired by Houdini, so has a lot in common with TouchDesigner (it's fully node-based, you can create audio reactive apps), and it works on the web, which makes scenes very easy to share.

Can I invite you to try Polygonjs as well?

you can generate an SDF from a mesh with [Polygonjs](https://polygonjs.com). Here is an [example scene](https://polygonjs.com/examples/bynode:mat:raymarchingbuilder...).

It won't generate a function, though. Instead it creates a 3D texture which is used inside the raymarching material. In my experience this is much more performant, and also art-directable.

(disclaimer, I'm building Polygonjs)

It sounds like you need a dynamic system that runs in the browser. Maybe try Polygonjs ( https://polygonjs.com )? The the 3rd interactive scene on the front page gives an idea of a dynamic model. I run it, if that of interest, happy to give more examples

If you ever wanted to do a vegetation modelling tool for the web, I invite you to try it on Polygonjs, it has a lot of similarities with Houdini (node-based, procedural modeling, HDA system, etc) and is all web/realtime. And open source.

This is extremely interesting: https://github.com/polygonjs/polygonjs/blob/master/src/engine/nodes/cop/SDFBlur.ts uses a 3D construct and implements the blur using a fixed matrix.