# Pointer in webxr is... short? 1ft. need it to be infinite

**URL:** https://forum.babylonjs.com/t/pointer-in-webxr-is-short-1ft-need-it-to-be-infinite/21869
**Category:** Questions
**Created:** [June 23, 2021, 8:09pm UTC](https://forum.babylonjs.com/t/pointer-in-webxr-is-short-1ft-need-it-to-be-infinite/21869 "2021-06-23T20:09:36Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![saitogroup](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/saitogroup/32/10624_2.png) [@saitogroup](https://forum.babylonjs.com/u/saitogroup)
#### Post date: [June 23, 2021, 8:09pm UTC](https://forum.babylonjs.com/t/pointer-in-webxr-is-short-1ft-need-it-to-be-infinite/21869/1 "2021-06-23T20:09:36Z")

</div>

hi, for some reason, the webxr pointer is very short, whereas, I want it to extend infinitely…

I’m not sure how/why I shortened it by accident.

I’m going for this kind of dynamic (I can tag a cube from far away bring it to me and throw it): [https://www.instagram.com/p/CQb23OQlSJ0/](https://www.instagram.com/p/CQb23OQlSJ0/)

Usually, my pointer is infinite, so I must have done something, but hard to figure out what… I’ve looked at my code carefully, and can’t find anything. So, I guess I’m asking what I should be looking for to fix this.

UPDATE:

I have a sphere surrounding the player; I made this sphere very small now, and it means that now “sometimes” the pointer extends infinitely. I almost have the feeling that it is pointing to and/or hitting invisible objects… so I’m currenly investigating what that’s about…

I’m realizing I may have another helper object around the player that is continuing to cause other interference; chasing it down; yeesh… OK, I’m going to define this as solved; it must be caused by my helper meshes…

@RaananW

---

<div class="post-metadata">

### Author: ![saitogroup](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/saitogroup/32/10624_2.png) [@saitogroup](https://forum.babylonjs.com/u/saitogroup)
#### Post date: [June 23, 2021, 8:54pm UTC](https://forum.babylonjs.com/t/pointer-in-webxr-is-short-1ft-need-it-to-be-infinite/21869/2 "2021-06-23T20:54:31Z")

</div>

it was caused by helper meshes; this was way trixsy

the more you know ¯\_(ツ)\_/¯

---

<div class="post-metadata">

### Author: ![RaananW](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/raananw/32/28955_2.png) [@RaananW](https://forum.babylonjs.com/u/RaananW)
#### Post date: [June 24, 2021, 9:31am UTC](https://forum.babylonjs.com/t/pointer-in-webxr-is-short-1ft-need-it-to-be-infinite/21869/3 "2021-06-24T09:31:17Z")

</div>

I love waking in the morning to solved questions on the forum 🙂

You can always mark the helper mesh as non-pickable (`mesh.isPickable = false`), it will then be ignored by the Ray.

---

<div class="post-metadata">

### Author: ![saitogroup](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/saitogroup/32/10624_2.png) [@saitogroup](https://forum.babylonjs.com/u/saitogroup)
#### Post date: [June 24, 2021, 4:25pm UTC](https://forum.babylonjs.com/t/pointer-in-webxr-is-short-1ft-need-it-to-be-infinite/21869/4 "2021-06-24T16:25:30Z")

</div>

Definitely getting to that point in the project where I’m creating fun new problems for myself by accident; re-factoring is at hand.
