Jump to content


Verified Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About apellisscot

  • Rank
  1. For me the latest SRanipal V1.3.2.0 fixed the issue and I am able to acquire the data at 120 Hz. Many thanks to the dev-team for all the support. @Damien Deltour: I had to update the runtime as well as the SDK. I'm using Unity 2019. Maybe this helps you...
  2. Hi @HackPerception, I think it is decently spec'ed: The CPU specs are quite similar to the one from @Corvus (Intel i7-9750H). In our system, we have a i7-10750H (see the comparison here). The GPU is the same (GeForce RTX 2070). Do you think I have to perform some additional configurations?
  3. Thanks @Corvus, it still captures data at a sampling frequency of around 60 Hz (see video attached). Sometimes the period drops to 8 ms, but this occurs rarely. Are there any CPU configurations to perform? I tried with deactivated hyper-threading, but did not have any luck. Soon we will have a higher performing PC to test with. I will let you know the results there. Eye Tracking 120hz 2021-02-15 13-44-20.mp4
  4. Thanks @Corvus, I had removed the call to "EyeMeasureDataWriter" and placed a static counter there - so similarly as you do. The only difference I see is that I register the callback in the Monobehaviour's "Start()" method and you do it in the "Update()" method. Although I do not see any reason why this should change something, I will give it a try next week. It would be great if you could send me the build. I've sent you a DM.
  5. Thanks @Corvus I followed your instructions and could still not reach the 120 Hz (instead, it is acquired at ~62 Hz). I tried v1 and v2 and only had a static counter incrementing in the callback function. Could it be that it is limited by our HW? We have following specs: Windows 10Pro Intel i7-10750H (specs can be found here) 32GB Ram GeForce RTX 2070 with Max-Q Design Following tool versions are used: SRanipal SDK & Runtime Unity 2019.4.18f1 Am I right in the assumption that the key limiting factor is the CPU and not the GPU? We wil
  6. Hi @prajaktakhandve, Do you have any updates on this? I was not able to reach 120 Hz. But could be based on the HW specs. I posted my issues here.
  7. Thanks for the answer @Corvus. Here's a code snippet, really basic. Note that I also checked without writing to the csv file in the callback method. Instead, I simply increased a counter in the callback method and logged the time at every 120th call. using System.Collections; using System.Runtime.InteropServices; using UnityEngine; using UnityEngine.Rendering.HighDefinition; using UnityEngine.XR; using System; using System.IO; using ViveSR.anipal.Eye; using ViveSR.anipal; using ViveSR; using Helpers; public class TestTracker : MonoBehaviour { private static EyeMeasureDataWriter _eye
  8. Hi everyone, I'm struggling with reaching the specified sampling rate of 120 Hz (8.33 ms) on a VIVE Pro Eye HMD. We use the SRanipal eye callback: SRanipal_Eye_v2.WrapperRegisterEyeDataCallback() in a script, derived from MonoBehaviour. The registered callback is only called every 14~16 ms, which leads to approx. 62 Hz. Way below the targeted 120 Hz. I think the PC specs are quite decent and should allow for 120 Hz sampling: Windows 10Pro Intel i7-10750H (specs can be found here) 32GB Ram GeForce RTX 2070 with Max-Q Design Following tool versions
  • Create New...