# Question about the data I can get from the ecs.input.SCREEN\_TOUCH\_START

**URL:** <https://forum.8thwall.com/t/question-about-the-data-i-can-get-from-the-ecs-input-screen-touch-start/5458>\
**Category:** Technical Support\
**Tags:** vps, studio\
**Created:** [March 9, 2025, 1:40am UTC](https://forum.8thwall.com/t/question-about-the-data-i-can-get-from-the-ecs-input-screen-touch-start/5458 "2025-03-09T01:40:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ken\_Mitsui](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.8thwall.com/ken_mitsui/32/163_2.png) [@Ken\_Mitsui](https://forum.8thwall.com/u/Ken_Mitsui)\
**Post date:** [March 9, 2025, 1:40am UTC](https://forum.8thwall.com/t/question-about-the-data-i-can-get-from-the-ecs-input-screen-touch-start/5458/1 "2025-03-09T01:40:50Z")

</div>

Hello!

I am writing a component for Niantic Studio.  
I have a question about the data I can get from the ecs.input.SCREEN\_TOUCH\_START event.  
When I output event.data to console, I get  
`{pointerId: 1, position: {...} , worldPosition: BN, target: undefined}`  
is outputted.

Outputting event.data.worldPosition yields  
`{x: -1.5845162968111624, y: -0.8738807687578227, z: 2.240194782272699}`  
is now output.

I think this is the location/worldPosition of the entity that was hit by a ray cast-like event during the SCREEN\_TOUCH\_START event, is this correct?

I am using this ([Studio: VPS Procedural | 8th Wall | 8th Wall](https://www.8thwall.com/8thwall/studio-vps-procedural)) as a reference to create a mesh from the bufferGeometry of the event.data obtained from the reality.meshfound event and add it to the scene.

What I want to do is to raycast to this mesh in SCREEN\_TOUCH\_START.

But currently, it seems that the rays are not hitting this mesh, but are floating a bit or a bit in front of it. And target is always undefined.

Do I have to add the target for SCREEN\_TOUCH\_START from ecs.createEntity()?  
If so, is it possible to set the bufferGeometry to the entity created by ecs.createEntity()?

---

<div class="post-metadata">

**Author:** ![GeorgeButler](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.8thwall.com/georgebutler/32/1903_2.png) [@GeorgeButler](https://forum.8thwall.com/u/GeorgeButler)\
**Post date:** [March 11, 2025, 3:41pm UTC](https://forum.8thwall.com/t/question-about-the-data-i-can-get-from-the-ecs-input-screen-touch-start/5458/2 "2025-03-11T15:41:44Z")

</div>

I’ll have to test this out, the screen touch events use a three.js raycaster under the hood so it should work.

---

<div class="post-metadata">

**Author:** ![Ken\_Mitsui](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.8thwall.com/ken_mitsui/32/163_2.png) [@Ken\_Mitsui](https://forum.8thwall.com/u/Ken_Mitsui)\
**Post date:** [March 11, 2025, 11:18pm UTC](https://forum.8thwall.com/t/question-about-the-data-i-can-get-from-the-ecs-input-screen-touch-start/5458/3 "2025-03-11T23:18:49Z")

</div>

Thank you for your answer!  
I see.  
So it is normal for the “target” to be null for the scene.added?  
Based on what you say, it looks like it could be due to the complexity of the mesh.

---

<div class="post-metadata">

**Author:** ![GeorgeButler](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.8thwall.com/georgebutler/32/1903_2.png) [@GeorgeButler](https://forum.8thwall.com/u/GeorgeButler)\
**Post date:** [March 11, 2025, 11:34pm UTC](https://forum.8thwall.com/t/question-about-the-data-i-can-get-from-the-ecs-input-screen-touch-start/5458/4 "2025-03-11T23:34:10Z")

</div>

I would say so, If you can get it working on a standard three.js project there might be something we can look into to learn why.

---

<div class="post-metadata">

**Author:** ![Ken\_Mitsui](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.8thwall.com/ken_mitsui/32/163_2.png) [@Ken\_Mitsui](https://forum.8thwall.com/u/Ken_Mitsui)\
**Post date:** [March 11, 2025, 11:46pm UTC](https://forum.8thwall.com/t/question-about-the-data-i-can-get-from-the-ecs-input-screen-touch-start/5458/5 "2025-03-11T23:46:37Z")

</div>

Roger that.  
I will try it with Three.js.
