three-mesh-bvh VS drei

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

I have been using react-three-fiber and react-three-drei - the react version of this project. The examples are over whelming and wonderful

https://docs.pmnd.rs/react-three-fiber/getting-started/examp...

One of my favorites is the image gallery. I modified this so that clicking on an image take you into another room (gallery).

https://github.com/pmndrs/drei is a collection of examples and helpers.

Most impressive to me is the one using a GLTF model, video textures on text, reflections and more. A standalone version is

https://bfplr.csb.app/

But even more impressive is the sandbox showing the not-very-many-lines-of-code at

https://codesandbox.io/p/sandbox/ground-reflections-and-vide...

A lot to putting a layer on top of threejs and I have run a fair number of head scratchers. But still the potential is huge. Using threejs has completely changed the way I look at website development. So if you are a svelte person I would definitely look into this.

the shader is here if you want it in vanilla https://github.com/pmndrs/drei/blob/master/src/core/Outlines.tsx though keep in mind it needs some additional work to support skeletons and instances, that's the code in the layout effect.

the eco system gives you so much freedom, especially when it comes to properly align, display your models, and to make them look nice. there are dozens of components for staging, lighting, soft shadows, you would miss out on all of that https://github.com/pmndrs/drei

there are more pain points than can be enumerated. i think you should take a look here https://github.com/pmndrs/drei and pmndrs in general. also the eco system it has covered so far.

there's a whole eco system around three in react and next. it starts with react-three-fiber, drei has tons of helpers, and then there's three-next for when you need 100% lighthouse, persisting canvas across routes etc.

Definitely ThreeJS and specifically React Three Fiber. React Three Fiber is an amazing wrapper around three that greatly reduces boilerplate. And because of how modular react is, the community has grown massively. With lots of helper components in the Drei library, and amazing examples in the author's Twitter. The Codesandbox is also a goldmine of example. And one of the best-produced courses by Bruno Simon to help you get started. He is the creator of this famous portfolio site.

I picked the stack I did to expand upon my skill set. In particular, I wanted to brush up on react-three-fiber, react-spring & drei.

what's the advantage of your version over this one by the developer who created react-three/fiber? https://github.com/pmndrs/drei/blob/master/src/core/OrbitControls.tsx I use the above by importing react-three/drei and it then works just like the one in your example