react-three-fiber VS use-cannon

this is perfect then. a large part of the threejs userbase is using https://github.com/pmndrs/react-three-fiber (roughly 1/4, and growing) and this is also where you find lots of job opportunities. fiber has a vast eco system, but if you can pair this with your knowledge of shaders you'll find a job tomorrow if you wanted.

there's 3d with threeJS you could play around with that and hooking it into react with react-three-fiber.

Have you looked at this: https://github.com/pmndrs/react-three-fiber

Only instance in recent memory where I was able to get something working with Expo but not the CLI was when trying to integrate react-three-fiber, but even that may be resolved now.

this will put you at a massive advantage: https://github.com/pmndrs/react-three-fiber it's a renderer, just like react-dom, it won't change what threejs is or how it functions.

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.

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.

I think the easiest for you would be to get into this through web development try this https://github.com/pmndrs/react-three-fiber coupled with this https://github.com/pmndrs/react-xr But don't expect super beautiful graphic from this, it's abstraction over three.js library which is abstraction over webgl standard which implements OpenGL ES 2.0 which is 7 years old graphics standard targeted to mobile devices with not much power. Or you can experiment with unity (unity XR) or unreal engine which are harder to learn but produce better graphics.

On the technical side, the ability to have pluggable renderers has been very useful for us. We never would have considered 3D without react-three-fiber. Building cli applications with react-ink is pretty cool.

Then, we need to install the dependencies that we will use in this project. We will use Three.js library, @react-three/fiber and @react-three/drei.

I'm using rapier physics lib in my own project, and i did that using workers too, i refered this repository https://github.com/pmndrs/use-cannon and when i saw the similar project to use physics lib into react-three-fiber but with rapier https://github.com/pmndrs/react-three-rapier, i notice that they don't use workers... There is some reason to not use workers with rapier? Weren't we supposed to use physics on workers for performance reasons?

For this example we are going to use Reac Three Cannon a specific library to create physics. You can use Rapier, another cool library, but is under development right now.

"Cannon" is the rigid body physics engine who includes simple collision detection, various body shapes, contacts, friction and constraints.

I'm trying to build a maze using react-three/fiber and react-three/cannon. I've added first person controls using this Minecraft Sandbox and a layout very similar to the example on the react-three/cannon Github page, just with more boxes acting as walls. But, instead of stopping at the boxes/walls, the camera moves directly in and through the larger ones and tumbles over the smaller ones. Any idea how to prevent this?

you use this library: [@react-three/cannon](https://github.com/pmndrs/use-cannon)

Since I'm a big Poimandres fan I looked into react-xr, and it was very easy to get a first WebXR project up and running. Unfortunately, there are many dependencies in the ecosystem which slowed me down: react-xr is built on top of react-three-fiber which is built on top of Three.js, and physics is enabled by use-cannon which is built on top of cannon-es. For a long time I was running into issues and helping fix them with a couple of pull requests, and ultimately it was preventing me from working on the actual project. Still, Poimandres is a great community and I got a lot of inspiration from the content being shared in the discord.

I'd be really curious to hear how you'd refactor a library like use-cannon? The primary challenge with it's development is exactly the issue that the other commenter described: building the API bridge between the WW and the main thread. I have been thinking about this for at least a full year and I haven't come up with a better way to structure the code - yet this seems like an ideal use case for a webworker.

There’s https://github.com/pmndrs/use-cannon for R3F physics too.

physics are easy, here's a 60 loc arkanoid using use-cannon: https://codesandbox.io/s/sweet-babbage-66cd7