Announcement

Collapse

TGC Tour - Congratulations!

Congrats to @Todd Morgan (NET) and @Joe_S (GROSS) winning the TGC1 2020 FALL TOUR - The RSM Classic !

Join this weeks TGC1 2020 FALL TOUR - Mayakoba Golf Classic. We are playing 2 rounds at Quarry Ridge Protee Pin 1: https://golfsimulatorforum.com/forum...a-golf-classic
See more
See less

Uneekor Eye XO - missreads

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Uneekor Eye XO - missreads

    Hy all
    Im having here and there some missreads on the Uneekor Eye XO. Initially, I had many missreads and the reason was a non-clean Win 10 pro installation. There were just too many services running in the background. Especially the Nvidia „rtx 2080 super“ driver created some issues. I understand that the ball data is calculated in real time on the PC. The Eye Xo does only transfer the ball pictures to the PC. So if there’re some services running in the background, that could be the issue here. Is anyone of you having similar issues? Anyones knows a service that should be killed to i prove that real time calculation?

  • #2
    I am seeing some misreads as well. Austin (Uneekor support) has remotely looked at my system a couple times, and some things have gotten better, but most are still there.
    Here is what I have seen:
    1. Driver misreads where it doesn't read a shot at all.
    2. Driver misreads that have a very high backspin and sidespin (greater than 8000 rpm backspin and 6000 rpm sidespin)
    3. The 888 & 222 rpm spin issue that the QED suffered from. Austin explained this is due to reflective surface on lob wedges. He gave me an update to try and that has helped a lot.
    4. TGC2019 sometimes get exactly half the backspin that the EYE XO is reading. For example, View software reads 11000, but TGC 2019 gets 5500 rpm. This issue started with the update Austin gave me.

    My system is an Intel i7 10700k and GTX970 graphics card. I have not troubleshooted any background processes, but it is a minimal Windows 10 install.

    What are the misreads you see?




    Comment


    • #3
      I have seen this a couple times using a GC2. It was exactly half and both times that I can recall it was 10000 and 9800. I wonder if it's something in TGC, usually you probably wouldn't get an exact spin that ends in 00 or 000.
      Originally posted by brockndsu View Post
      4. TGC2019 sometimes get exactly half the backspin that the EYE XO is reading. For example, View software reads 11000, but TGC 2019 gets 5500 rpm. This issue started with the update Austin gave me.





      Comment


      • #4
        Number 4 is definitely an issue with TGC. I've seen it with GC2 and QED

        Comment


        • #5
          Number 4) Turn OFF high backspin correction in the settings file.

          Comment


          • #6
            Originally posted by brockndsu View Post
            I am seeing some misreads as well. Austin (Uneekor support) has remotely looked at my system a couple times, and some things have gotten better, but most are still there.
            Here is what I have seen:
            1. Driver misreads where it doesn't read a shot at all.
            2. Driver misreads that have a very high backspin and sidespin (greater than 8000 rpm backspin and 6000 rpm sidespin)
            3. The 888 & 222 rpm spin issue that the QED suffered from. Austin explained this is due to reflective surface on lob wedges. He gave me an update to try and that has helped a lot.
            4. TGC2019 sometimes get exactly half the backspin that the EYE XO is reading. For example, View software reads 11000, but TGC 2019 gets 5500 rpm. This issue started with the update Austin gave me.

            My system is an Intel i7 10700k and GTX970 graphics card. I have not troubleshooted any background processes, but it is a minimal Windows 10 install.

            What are the misreads you see?
            Same here

            1) Not only driver. The ball gets recognized, red LEDs are on, but he doesn‘t get the shot
            2) Not only driver but mainly. I had situations with -10k backspin
            3) same here. But I doubt the explanation. I did a fresh installation of Windows 10 Pro without any drivers, and it works much better.
            4) didn‘t see that but will have an eye on it, thx.
            5) Putts get a total missread of spin and direction. Yesterday, a put went 45° left
            6) Sometimes he reads the tylormade (they have a white stripe on it) driver as a ball e.g. when doing a trial swing. Same with white tees, but I‘m not using white tees anymore.

            I‘m sure it has to do with the processes and services running real-time.

            great if we can increase the pressure towards uneekor here. I‘ll reach out to them as well. So far Oliver did and I reached out to Oliver only, thinking its solely an Issue I have.

            Comment


            • #7
              I‘ve posted the TGC related problems in another conversation where Protee is potentially reading. Anyhow, I understand that TGC2019 is a dead product. An expensive product for being dead. Honestly the first bounce issue is known since Day 1 and would only take 1h to be resolved, but nothing. Anoying.

              here the link to the other conversation. https://golfsimulatorforum.com/forum...ub-2019/page37

              Comment

              Working...
              X