Announcement

Collapse
No announcement yet.

TGC seems really penal on side spin

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

  • TGC seems really penal on side spin

    I had a range session using Skytrak software, then followed it up with a round on TGC. It really seems to me that TGC is way more penal for side spin than Skytrak is. I looked at the side spin numbers and they looked right, but the results had the ball slicing and hooking in TGC whereas the same was giving a lesser fade or draw in Skytrak. Any thoughts?

  • #2
    Yes I've noticed this as well. Higher loft the worse it seems to me

    Comment


    • #3
      I agree 100%

      Comment


      • #4
        I hope this is addressed right away - it's almost unplayable, you really have to compensate for either a fade or draw

        Comment


        • #5
          I guess TGC has its own flight model. Given parameters it generate different type of flight mode which you guys don't like.

          Comment


          • #6
            It's not really about liking or not - the skytrak range has been tested against different products for its accuracy so you wouldn't think there would be much difference between it and tgc but there is

            Comment


            • #7
              st_golfer and goatbarn If you look at this thread "TGC for SkyTrak Interface Update​" - SkyTrak_Seth said it would be fixed. It would be nice to have a comment from ProTee United to confirm that this is an issue with sending the spin data from skytrak to TGC and not an algorithm that is that much different from the skytrak range.

              Comment


              • #8
                The issue I have is with the algorithm

                Comment


                • mthunt
                  mthunt commented
                  Editing a comment
                  I agree. Some of the algorithms are off. If I hit a low spin drive (1200 back and 500 draw) it falls out of the sky. As a rule of thumb, Trugolf told me you need 500 rpm of side to get an 8 to move. I was outside yesterday and 500 barely was hardly a draw. It TGC, it'll move too much. Also, I find wind to penile. A 10mph side wind moves the ball too much. Also, spinning back wedges from the rough. That needs to be fixed.

              • #9
                I was hoping it was part of the bugs with Skytrak and TGC and not an algorithm issue as that is unlikely to be changed. Do you know if there has been discussion on this with the GC2 guys? From about 8iron to wedge the side spin is completely exaggerated compared to both skytrak range and the e6 demo both of which I think are pretty accurate.

                Comment


                • #10
                  I suspect, this is something Protee needs to fix. Skytrak doesn't give the flight model to Protee based on the interface specs I have seen.

                  Comment


                  • #11
                    Opticsguru Do you use skytrak or GC2? hopefully we can get a comment from ( ProTee United ) if this is something that is going to be addressed or not
                    Last edited by GSF_Admin; 03-13-2016, 02:50 PM. Reason: Name removed. Do not post personal details.

                    Comment


                    • #12
                      I use skytrak.

                      Comment


                      • #13
                        Originally posted by goatbarn View Post
                        The issue I have is with the algorithm
                        I agree. Some of the algorithms are off. If I hit a low spin drive (1200 back and 500 draw) it falls out of the sky. As a rule of thumb, Trugolf told me you need 500 rpm of side to get an 8 to move. I was outside yesterday and 500 barely was hardly a draw. It TGC, it'll move too much. Also, I find wind to penile. A 10mph side wind moves the ball too much. Also, spinning back wedges from the rough. That needs to be fixed.
                        Edit Flag
                        My Courses:
                        World Par 3's by mthunt
                        Toronto GC (L) mthunt
                        Burlington G&CC by mthunt
                        Weston G&CC by mthunt
                        London Hunt Club L mthunt
                        Park CC Lidar mthunt
                        Sunningdale GC Robinson L
                        Sunningdale GC Thompson L
                        Muirfield Village (liDAR) First Ever Lidar course
                        Country Club of Castle Pines (liDAR)
                        The Sanctuary GC ProTee L
                        The National GC L mthunt
                        Mississaugua GC L mthunt
                        Shaughnessy G&CC L mthunt
                        Markland Woods CC mthunt
                        Hidden Lake Old L mthunt
                        Magna GC L mthunt
                        Barrie CC L mthunt
                        mthunt Range

                        Comment


                        • #14
                          Glad it isn't just me

                          Comment


                          • #15
                            Originally posted by TRenn View Post
                            st_golfer and goatbarn If you look at this thread "TGC for SkyTrak Interface Update​" - SkyTrak_Seth said it would be fixed. It would be nice to have a comment from ProTee United to confirm that this is an issue with sending the spin data from skytrak to TGC and not an algorithm that is that much different from the skytrak range.
                            Now that the update is out for public consumption, I installed it last night and will test out some either later today or (more likely) tomorrow.

                            Comment


                            • TRenn
                              TRenn commented
                              Editing a comment
                              Let me know if you find a difference with the side spin
                          Working...
                          X