Cody Bennett

The issue is that controls' spherical orientation is not updated, so when the gizmo is done animating, the controls reverts back to its stored state.

We'll need to see what exactly enabled that behavior upstream in three. Until then, you can use theirs directly: ```jsx import { OrbitControls as OrbitControlsImpl } from 'three/addons' import {...

@drcmda, what was the point of eda982937b0f91e0e469a41b679bcd07831650b1?

This needs testing and I've since been traveling. If it looks good to you, then sure. I need to add a Storybook entry since Edges doesn't seem to have one.

Which Next.js version? We've seen relentless regressions on their side related to the App Router and I can only suggest pinning. 14.0.1 was known to work. We employ integration testing...

If you want to test out the PR, try: ```js { "dependencies": { "@react-three/drei": "https://pkg.csb.dev/pmndrs/drei/commit/47d99046/@react-three/drei" } } ``` I need to figure out why our integration tests for CRA are...

I think you need to take this up with Next.js upstream and/or pin to an earlier version. Something is seriously wrong with bundling as that code shouldn't be evaluated on...

Please see my last comment. There is an issue in the Next compiler we can't work around and requires either a previous version or a fix upstream.

WebGPURenderer is still heavily under development, and there's no user-facing API at this time. It may be at least a year until this is even possible as experimental, but that's...

One reason for storing its own group reference instead of an id is that the id is volatile when instances unmount. So, maybe we still store the id, but notify...