Tweet
Hi,
I have the VisTrak IRVC launch monitor and TGC 2019 software. Sometimes after I change clubs in TGC (on driving range or playing a course), the launch angle data gets stuck on the previous shot and can sometimes get stuck for multiple shots. It does this whether the launch angle is estimated or measured.
For example, lets say I hit a pitching wedge and measured a launch angle of 30deg. Then in TGC, I change my club to a 4-iron, take a shot, and TGC says the launch angle was still 30deg when it clearly wasn't. The shot distance is then really high which isn't good. When I open the VisTrak video feed, it shows the launch angle was more appropriate for a 4-iron, say 17deg.
So either TGC isn't accepting the right launch angle or the VisTrak CP just isn't sending the correct info to TGC. It seems to get unstuck if I change clubs again or I open the VisTrak video feed.
This is a frustrating problem when playing a round of golf. Anyone else experience this issue? I'm running the latest Control Panel, v9.4.9.8 and this problem has occurred with some previous versions as well.
Thanks.
I have the VisTrak IRVC launch monitor and TGC 2019 software. Sometimes after I change clubs in TGC (on driving range or playing a course), the launch angle data gets stuck on the previous shot and can sometimes get stuck for multiple shots. It does this whether the launch angle is estimated or measured.
For example, lets say I hit a pitching wedge and measured a launch angle of 30deg. Then in TGC, I change my club to a 4-iron, take a shot, and TGC says the launch angle was still 30deg when it clearly wasn't. The shot distance is then really high which isn't good. When I open the VisTrak video feed, it shows the launch angle was more appropriate for a 4-iron, say 17deg.
So either TGC isn't accepting the right launch angle or the VisTrak CP just isn't sending the correct info to TGC. It seems to get unstuck if I change clubs again or I open the VisTrak video feed.
This is a frustrating problem when playing a round of golf. Anyone else experience this issue? I'm running the latest Control Panel, v9.4.9.8 and this problem has occurred with some previous versions as well.
Thanks.