Three.js has an imperative/stateful API for constructing and updating objects, not dissimilar to the DOM. So if your state lives in a separate place, then just like the DOM, you'd have to imperatively patch the view state to keep it in sync. Adding a layer that does this syncing automatically makes a lot of sense to me.
Doing it through React seems a little bit odd... but I haven't looked closely enough to understand why/whether this coupling is actually necessary
Doing it through React seems a little bit odd... but I haven't looked closely enough to understand why/whether this coupling is actually necessary