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?
Announcement
Collapse
No announcement yet.
TGC seems really penal on side spin
Collapse
X
-
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
-
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.
-
-
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
-
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
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.Originally posted by goatbarn View PostThe issue I have is with the algorithm
Edit FlagMy 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
-
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.Originally posted by TRenn View Postst_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
Comment