Thank you very much. I updated the Unity version, and the previous issues have been resolved. I believe I have completed all the steps; however, when I test the system while wearing the glasses, no ray is displayed. I am unsure how to proceed at this point. Specifically, after verifying the Neon–Unity connection, how can I further confirm that eye gaze is being recorded correctly and proceed with integration for AOI testing?

Hi @user-b5a8d2 , it looks like you have everything installed and connected correctly. The gaze ray is not visualized by default, because this would be distracting to participants during an experiment and would obscure their vision.

To confirm that the data is being received, you could simply print it out to Unity's Console. Since you say "recorded", are you expecting that the Neon Companion app automatically records VR data?

In any event, if you want to enable gaze ray for testing/development purposes, then you need to check Do Raycast and Raycast Pointer Visible. Alternatively, as suggested in the installation instructions, you can take the Gaze Data Visualizer code and modify it to make your own visualizer.

Hi! I want to get pupil diameter data in unity 3d. I am using neon xr core package and have done all the necessary settings and steps as described in the pupil labs website. I am unable to get the data in unity.

I have tried UDP off and on using config file. Every time the same issue - it connects (Live555 client shows started playing session), after a few seconds streaming stops (sending request: teardown and closing stream). And the cycle repeats.

I have also tried switching networks and no change.

Is this a known issue? Are there any fixes I can try. Also let me know if more info is needed

Hi @user-aadf20 , what kind of network are you using and what version of the Neon Companion app are you running?

Right now, I am using a wifi network. I have also tried with my mobile hotspot as well. But the same issue persists. The companion app version is 2.9.31

Thanks, and are you using the latest version of the Neon XR Core Package from last month?

My neon xr core package version is 2.0.0

Thanks, and you installed it from the Github link in the instructions within the last month?

Yes

Hi! I’m currently using Neon with Unity to receive gaze data. For saccade and fixation detection, it seems some post-processing is required. Do you happen to know what parameters or algorithms Pupil Labs uses internally for this post-processing, or if there’s any related documentation/site available? When I compared the results exported from Pupil Labs with my own implementation, the detected saccades and fixations showed somewhat different patterns, so I’d like to better understand the parameters/settings used by Pupil Labs.

Hi @user-b5a8d2 , rather than trying to re-implement the algorithms, it would probably be easier to make use of the fixation information that is already exposed by the underlying client. Check out the Streaming sample in the Neon XR Core Package. You can open it by going to the Package Manager, selecting the Neon XR Core Package, and then clicking on the Streaming sample entry. See this message for more details: https://discord.com/channels/285728493612957698/1187405314908233768/1494345333386510470

Otherwise, you can use Neon's Events to align the Neon XR (https://discord.com/channels/285728493612957698/1187405314908233768/1479799164849225870) and the recorded Neon data on the phone and then use this script to apply the mount calibration post-hoc. To clarify, you can stream and record at the same time.

Hi, I have historical CSV files from recordings where I only captured 2D gaze coordinates from the Companion App (without the VR video). To meaningfully analyze this data within my 3D VR context, I need to add depth information and convert these 2D points into 3D coordinates in the VR world. Is there a Python script to transform these 2D scene camera coordinates to 3D VR coordinates? Thanks so much!

Hi @user-d43541 , we received your email and will respond there and here today

Hi @user-d43541 , first, apologies about that. I had actually finished a script back then, but completely lost track to share it with you.

Can you try the script here? I will try to add an easy time sync component to it tomorrow.

Thank you again.

I am now preparing the input files to run the script. Could you kindly clarify whether the script is designed to read the files recorded with timestamps from the Android phone backend, or the original files downloaded from Pupil Cloud?

It is designed for the Native Recording Data, which you can obtain directly from the phone or from Pupil Cloud by right-clicking and choosing Download > Native Recording Data. If you have a Moto Edge 40 Pro or Samsung S25 Companion Device, then the eyetracking data in the Native Recording from the phone will be at 200 Hz. If downloaded from Pupil Cloud, then it will be at 200Hz, regardless of the phone.

Hi Pupil, I’m running a 15-subject study using the Pico 4 Ultra and the Neon MRTK3 sample app to calibrate before switching to my custom prototype. I’ve hit a workflow blocker: the Home button on the Pico 4 controller doesn't function while inside the MRTK3 sample. Because I can't exit the app to the system menu, I currently have to completely reboot the headset between every single subject. Is there a known fix, or a specific MRTK setting I need to tweak to re-enable the Home button so I can exit the app gracefully? Any help is appreciated! Thank you

Hi @user-4c288b , the Neon XR team tried to reproduce this, but it is not happening on our end. What Pico SDK version and which Pico OS version are you using?

Hi @rob , thanks for looking into this! Here are my exact versions: Pico OS Version: 5.15.5.u Pico SDK Version: 3.3.3

One important clarification: I am not building the MRTK3 sample from the Unity source code myself. I installed the pre-compiled APK directly from the download link on your official website.

Thanks. The team will re-build it with the newest Pico SDK, in case that is relevant to the issue. In the meantime, did you always have this issue or was it previously working for you before?

Hi @rob , Yes I always had this issue.

Thanks for the clarification, @user-4c288b . We have uploaded the new build of the APK to the link in our Documentation. Can you uninstall the version that is currently on the headset and try with this new version?

Thanks for your reply @rob , I install the new version downloaded on the link you provided , And still , the Home button isn't functioning neither pressing nor holding. No way to quit the app

Hi @rob , I am using the Neon Companion app on a Google Pixel, but it is not working. I wanted to know whether I need to use the device (Motorola ) that is provided by the company when I bought it.

Hi @user-9c79e4 , indeed, the Google Pixel is not a supported device. You can see the list of supported devices and Android versions here. So, yes, you would want to use the Moto 40 Edge Pro that was shipped with Neon.

@rob Thank you for the reply. As the Moto 40 Edge Pro device is not working, I will order it on Amazon with the same specifications. Will it work, or should I re-order from the pupil labs?