So, I’m having this issue with my Skytrak (skytrak app on a PC) where swing speed is not even in the ballpark, yet the distances are pretty accurate.
let’s take a 6 iron for example. On a trackman I swing 86-88mph, on the skytrak it’s showing me anywhere from 62 - 79mph.
but here’s the kicker: the distances are fairly close, which should be impossible. Earlier I hit one 184 yards but the swing speed was 74mph. If I hit one a little fat and maybe it travels 165-175 it will register club speed in the 60’s.
now, I know it’s a calculated speed, but ball
speed is off too. I’ve seen ball speeds from mid 90’s to low 100’s. But the distance is accurate.
in fact, save for my wedges, my irons, distance side are spot on. The wedges however are under reporting distances big time. My 46 degree that I hit on the course 120-135 travels barely 95-100 in the skytrak.
Note also that in TGC 2019 the club speed seems a lot more accurate in the skytrak.
Anyone have any idea as to what the issue could be? What’s baffling me is that If it’s calculating a slow swing, the distance should be cut, but it’s not. Seriously thinking of switching to the mevo+ if I can’t fix this issue.
let’s take a 6 iron for example. On a trackman I swing 86-88mph, on the skytrak it’s showing me anywhere from 62 - 79mph.
but here’s the kicker: the distances are fairly close, which should be impossible. Earlier I hit one 184 yards but the swing speed was 74mph. If I hit one a little fat and maybe it travels 165-175 it will register club speed in the 60’s.
now, I know it’s a calculated speed, but ball
speed is off too. I’ve seen ball speeds from mid 90’s to low 100’s. But the distance is accurate.
in fact, save for my wedges, my irons, distance side are spot on. The wedges however are under reporting distances big time. My 46 degree that I hit on the course 120-135 travels barely 95-100 in the skytrak.
Note also that in TGC 2019 the club speed seems a lot more accurate in the skytrak.
Anyone have any idea as to what the issue could be? What’s baffling me is that If it’s calculating a slow swing, the distance should be cut, but it’s not. Seriously thinking of switching to the mevo+ if I can’t fix this issue.
Comment