This behavior typically occurs when movement logic relies on keyboard events that stop updating correctly after a period of inactivity, or when the component's state freezes due to stale closures . In React Three Fiber, it can also be related to the render loop ( useFrame ) entering a low-power state or to the window losing focus.

I would specifically review how you're handling key state, whether the movement is executed within useFrame , and if there are any optimizations that suspend updates when there's no interaction. Sharing the component code and input logic would help pinpoint the exact cause.