I have found for the most part the Skytrak does a good job of capturing most of my swings, although it seems that some sessions perform much worse than others. I don’t leave my skytrak in a permanent location, but set it up each session (indoors), so its position relative to my mat is always changing (slightly), and so are the golf balls I use....Which could be part of the issue…
One of the challenges I find, is that on misreads there is no feedback provided by the software. I think it would be a better experience to have the software acknowledge a hit, and provide some feedback on the issue. I understand this wouldn’t be possible for those cases when it doesn’t event detect any sort of hit, but for most of the cases I'm assuming it does register something, but just doesn't have enough quality info to calculate the flight...
There must be a certain standard set of scenarios that cause misreads such as the ball where it can’t identify dimples/characteristics, having the ball misplaced relative to the laser (not giving the camera enough capture range), etc. For example, I find certain balls cause more misreads that others (something with the ball), in other cases for chip shots I need to put the ball a couple inches behind the laser to get it to pickup (something with the location).
It would be a huge help to have the unit provide feedback on these misreads, to let the user know what could be corrected rather than having to guess what the issue is. Currently it's just a black box...in more ways than one
This may also help reduce the load on customer support, where people assume it's a flaky unit, but it’s something that could be corrected by the user.
Thoughts? There are a ton of posts on misreads, so this would seem to provide a lot of value...
Next question: Why does it always seem to do the misreads when I finally feel like I hit the "perfect shot"???
One of the challenges I find, is that on misreads there is no feedback provided by the software. I think it would be a better experience to have the software acknowledge a hit, and provide some feedback on the issue. I understand this wouldn’t be possible for those cases when it doesn’t event detect any sort of hit, but for most of the cases I'm assuming it does register something, but just doesn't have enough quality info to calculate the flight...
There must be a certain standard set of scenarios that cause misreads such as the ball where it can’t identify dimples/characteristics, having the ball misplaced relative to the laser (not giving the camera enough capture range), etc. For example, I find certain balls cause more misreads that others (something with the ball), in other cases for chip shots I need to put the ball a couple inches behind the laser to get it to pickup (something with the location).
It would be a huge help to have the unit provide feedback on these misreads, to let the user know what could be corrected rather than having to guess what the issue is. Currently it's just a black box...in more ways than one
This may also help reduce the load on customer support, where people assume it's a flaky unit, but it’s something that could be corrected by the user.Thoughts? There are a ton of posts on misreads, so this would seem to provide a lot of value...
Next question: Why does it always seem to do the misreads when I finally feel like I hit the "perfect shot"???