Hi, we recently purchased the Pupil Labs Meta Quest Integration. While attaching the eyetracking module, we noticed that the included screws appear to be too short and do not reach the threads on the VR module. Is this a known issue? Could you please advise on the correct screw length/specification and whether we can order longer replacement screws? Thank you!
Hi @user-861e5b , which screw did you try tightening first? Sometimes, you need to screw the right one before the left, or vice versa.
If that does not resolve it, could you open a Support Ticket in 🛟 troubleshooting about this? Thanks.
Hi there. We are using the neon glasses in combination with VR at our experiment in the lab. We have a simple navigation task made in Unity. Since the camera of the neon glasses is not able to record the VR-environment, we were wondering if there's a simple function in Unity to synchronize the start of our experiment with the start of recording the pupil data. Thanks in advance!
Hi @user-c833f8 , I moved your message to the 🤿 neon-xr channel.
Have you tried the neon-vr-recorder tool? We are currently upgrading it to send synchronization Events that will be usable in the new Neon Player Beta (https://discord.com/channels/285728493612957698/733230031228370956/1458459857693704222).
Otherwise, you can send Events to Neon from Unity for time sync. It only requires sending a properly formatted JSON packet in a HTTP POST request.
Thanks - we'll take a look into it!
You are welcome. Just let us know if you have questions.
Hello! Can the new Neon Player (beta) player be used with recordings that don't include scene video? I am trying re-process some recent recordings made with the Neon module mounted in the Quest3 XR frame. These don't include scene video files, since the front-facing camera wouldn't have captured anything while mounted in the VR headset, but the beta player seems to expect it (it throws errors when loading the Native Recording Data, which I'd be happy to share).
This use-case wasn't really considered for the initial release, but if you can share your recording, I can take a look to see how much effort it would take
Hello! For integration (i.e. https://pupil-labs.com/products/vr-ar), does the gaze-tracking module fit into "Pico 4 Ultra" (i.e. https://www.picoxr.com/uk/products/pico4-ultra )? Also, do you provide examples of gaze-driven applications (like you show on the pupil labs page), so that one can build upon them. Thank you.
Hi @user-c541c9 , yes, our Pico 4 mount does fit into the Pico 4 Ultra.
Regarding gaze-driven examples, you can use our MRTK3 Examples as a reference point for coding and building custom applications. The Neon XR Core Package that it is built upon is for Unity, but is SDK-agnostic. It can also work with the XRIT and the Meta SDK, for example.
Will you be using Unity or a different environment?
Hey Pupil Labs team! We recently got our NEON with the mount for the PICO 4. First off: amazing device and I was (originally) ultimately pleased with the snug fit of the mount/face mask into the HMD. However, the cables on the mount reach into the visual field, covering a relevant part of the lens, and being pretty annoying when actually using the HMD. Is there any way to improve that? At VSS, I tried the LABO (silico labs) demo with the Quest 3, and I did not notice any similar issues. Maybe there's more space in the Quest 3 as compared to the PICO 4, but as is, it's quite a throwback for using it with the PICO, I have to say. Would be great to find a solution – if possible. (I'm in Berlin, btw, if that helps. 🙂 )
Hi @user-141bcd 👋 ! Thanks for the kind words! The Meta Quest 3 uses a different facial mask completely. The Pico 4 mount is embedded inside the headset, and for it to fit flush, you’ll need to modify the padded face attachment slightly.
Steps: 1. Identify the section of the padded face attachment that needs to be cut. See Image (1) for the exact location on your device. 2. Carefully cut out this section. We suggest using a very sharp 3mm drill bit for the cleanest result. Alternatively, you may use a sharp blade or dremel tool, but proceed with extreme care. 3. Insert the Neon Pico 4 mount into the Pico 4 headset, then add the padded face attachment ensuring the Neon cable is routed through the newly made opening. Confirm that the mount is secure and the mask is correctly installed.
See Image (2) for a reference of the completed setup.
Once mounted, you can gently pull the cable to help the curved wires sit more snugly along the PCB.
Hi @user-d407c1 , thx for the quick response! That's also a good piece of advice. However, that does not solve my main issue. Sorry if I was unclear. I'm referring to the cables in front of the lense which partly block the sight of the user.
Once mounted, you can gently pull the cable up, to help the curved wires sit more snugly along the PCB, they would still protrude slightly since they need to be soldered to the PCB, but they can go a bit tighter around, invading less space on the FoV.
thx, @user-d407c1 ! That helped. I'm attaching a picture of the "modified" version for potential other users. I would not have dared bending these cables. It's substantially better now, although the cables are still visually noticeable. I can live/work with that version. However, if you don't mind honest feedback: to match the excellence of the rest of the device and the very nice 3D print / face mask, the cable placement can still be improved. I'm not a hardware-person, but it seems like there's enough space to have the cables go inwards (i.e., towards the nose) directly. Thx for the quick support!
Thanks! I'll pass the feedback to our hardware team to see if there is anything that can be done.
