Why button triggers overlapping between on-screen buttons and AR buttons?

Hello. I’m developing a WebAR experience that have buttons on-screen and AR buttons.

Capture

Sometimes when the on-screen buttons and AR buttons are too close (not on top of each other but just really close together) clicking on AR button triggers the on-screen button function instead. Why does this happen and how to avoid this?

The on-screen buttons have action On Tap > Launch Web Link. The AR buttons functions are in a script that has the event pointerdown.

1 Like