react-three-fiber VS polygonjs

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.

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.