Manually triggering pointer event intersections?

[JacobJaffe]

Hello -- I'm using the event system to manage selection of objects in my scene (a user can mouse over an object, and drag it).

The user is also able to move the camera. However, when the camera moves, the pointer doesn't necessarily move, so no onPointerMove event occurs. This causes the perceived hovered element to be incorrect until the next pointer event occurs.

Moving Mouse, WITHOUT camera movement:

Moving Mouse, WITH camera movement:

Ideally, I'd like to fully utilize the existing system by triggering another onPointerMove event. Initially I looked into manually creating a SyntheticEvent to trigger this via react, but it looks like that's not really possible outsound of using a test utility system for mocking an event.

Is there a direct way of triggering an event (or RE triggering a previous event)?

Ideal scenario:

  if (code === "KeyA") {
    moveCameraLeft();
    triggerNewEventRaycast(); // <-- can't figure this part out!
 }

[drcmda]

yes, you can.

const { intersect } = useThree()
...
intersect(event)

it's defined as

intersect: (event: DomEvent | undefined = {} as DomEvent, prepare = true) => handlePointerMove(event, prepare),

it's kind of an escape hatch. you can inject a fake event (or a real one), prepare means that it will set up the raycaster to pierce the scene according to the events coordinates (offsetx/y) otherwise it will take the last known coordinates. it will then call pointerover/out and move on all registered handlers whose objects are hit.

you can in theory also call the real events directly, they're all part of the internal state

const { events } = useThree()
...
events.onClick({ nativeEvent: { offsetX: 100, offsetY: 100 }, type: "click" })
events.onPointerOver(...)
events.onPinterMove(...)
...

[JacobJaffe]

Thank you! This works great for my use case here.
I can't seem to get the "last known coordinate" behavoir to work correctly as how you described though.
e.g.

intersect(undefined, false); 

does not seem to fire the raycast at all

It also looks to me like the typescript declarations are incorrect -- maybe related? (Or I'm missing something here?)

canvas.d.ts, for 5.3.10

    intersect: (event?: DomEvent) => void;

Regardless, I'm able to get this to work now by manually keeping a reference to the native event and explicitly using it in the computeOffsets of the raycaster:

    raycaster={{
          computeOffsets: (event) => {
            if (event && event.nativeEvent) {
              const { offsetX, offsetY } = event.nativeEvent;
              lastKnownOffset.current = { offsetX, offsetY };
            }
            return lastKnownOffset.current;
          },
        }}

Thanks again!!

[SmileyJames]

The API in v6 seems to have changed for this use case

What alternative method has this been replaced with?

Is this the correct method now (un tested):

  const { events } = useThree();
  events.handlers?.onClick(new Event("click")

[drcmda]

thats correct, keep in mind that if you dont give it correct x y it wont raycast the mesh you're trying to target.