—

@Mugen87 @KodyJKing this looks 😍, just a detail: this is not a correct import, it should just be `three`: ```jsx } from '../../../build/three.module.js'; ``` and the normalRenderTarget should probably be...

It works slightly different look into drei/cycleraycast as an example Ps drei/pointerlock automatically Centers it, there is no reason to do it by hand, you can also look into that...

ps https://github.com/pmndrs/drei/blob/master/src/core/PointerLockControls.tsx ```jsx React.useEffect(() => { if (enabled) { controls.connect(explDomElement) // Force events to be centered while PLC is active const oldComputeOffsets = get().events.compute setEvents({ compute(event: DomEvent, state: RootState) {...

im not sure, tail usually indicates end of a series of frames. if im not mistaken it isn't called in frameloop=always because there's no "end". imo if frames are called...

IMO invalidate is also no indication for tail. Tail is when rendering is demand and you rotate controls, once it stops calling invalidate tail is called. Invalidate basically just counts...

@haywirez is there a test or a sandbox somewhere? and if it's really as easy as adding the events, what speaks against adding them all like @FarazzShaikh said? also, how...

that's expected behaviour. i think even the dom operates that way. but either way it would cost too much to run raycasting on every frame. if you want that you...

sounds like a good idea. just as someone that has never used physical lights before, is it harder to control? even without knowing the math, these are just higher numbers,...

where do you see a hard dependency in zustand? https://unpkg.com/browse/[email protected]/package.json i only see peer: ```jsx "peerDependencies": { -- 71 | "react": ">=16.8" 72 | }, ```

i have removed the duplicated and made is.equ more generic, it can now compare arrays and objects shallow or by reference, which should now suit all usecases.