SkyTrak Reproducible Misreads Making TGC 2019 Society Tours Unplayable?

[hankydysplasia]

Hi hankysyplasia,

I assume you have not had any updates on this. Just to confirm, these reads happen in both TGC2019 and in Skytrak range?

I played real golf this summer and haven't played TGC since spring. (First year after having a simulator, and actually came away with several rounds under par for the first time in more than a decade.)
Started back up with the wizardofcoz league yesterday. Had a misread 6i that was around 3200 rpm and a good 7i, so still happening. Honestly don't use the skytrak range software much.

If they're doubling at that launch angle as well, maybe its a camera blind spot. No idea why it would do that.

Thanks for keeping up on this. Glad to see someone cares in investigating it. Skytrak has continued to ignore emails.

[Morini]

In the facebook group, frequent GSF poster Mirek said that he had the same problem, and identified the FMJ as a cause.

I have always felt that FMJ can cause issues. This makes a lot of sense. In order to get reads over a wider range of launch angles, I think the unit has an algorithm that can read partially captured balls. This would typically be the case for very low (going below field of view of first imager) and also very high (going above field of view of second imager). I wonder if for some reason 20 degrees in an FMJ somehow causes a blind spot of sorts, partially obscuring the ball for either of the imagers.

If the unit does attempt to read partially obscured balls, there could be a situations where there are two possible ball rotations due to the limited overlap of ball markings between images. If so, it is possible that that the system uses ball speed for disambiguation. Or maybe it merely calculates/guesses at spin if it can't find overlap. That is not as far fetched as it sounds ... the R10 does a decent job guessing spin for ALL shots. It does have the benefit of measured club head speed of course.

Hanky, you may want to try without the FMJ to see if the error persists. There will be a small risk of course. I have never hit the unit in tens of thousands of shots, but it is greater than zero.

Seth himself said that he had similar ball speeds, but who knows, maybe seth doesn't use FMJ ... because the risk is low, and it saves him time, and of course, the repair shop isn't far away.

[Morini]

I should add that I don't own an FMJ, but it would be interesting to hold an alignment rod or similar at a 20 degree angle from the red ball placement dot to check whether the FMJ cut-outs cause problems at that angle.

Since the timing between the strobes is fixed (4.12 milliseconds), the horizontal ball position relative to imager is unique (and fixed) for a given ball speed... which would explain why some ball speeds trigger this bug more than others.

For example, for every single 130 mph 20 degree shot, the ball is in a specific position relative to imager. Only at that speed and that trajectory will it be found exactly there (within laser curtain margin of error). This would totally explain it.

[Morini]

Hankydisplasia, if you happen to see this, please try with case off. There is more and more anecdotal evidence that specific ball speed and trajectory combinations causes either high or low spin. The FMJ could definitely be the cause of that. Easy test.

[Morini]

Nevermind. It is not the FMJ. I am now getting the same bug, almost exactly like Hankydisplasia. It makes TGC2019 very difficult to enjoy, because it is a common distance on the courses we play. And we can probably rule out the FMJ, because I don't use one, and still have the issue.

[Morini]

Any news or updates on this. It is most certainly a thing. My son can't use 7 iron on TGC2019 any longer, or he will sail the green by 20 yards most of the time. There is something special about this combination. I am guessing that this exact ball speed & trajectory combo puts the ball in a blind spot of some sort. But partially ball imaged ball usually results in random whacked HLA, but this bug only affects total spin, so maybe it is something else, like flawed logic in the image engine. I hope it is because then there is hope it can be fixed.

If you don't know what I am talking about, check out the TXG video with the skytrak. Halved or quartered spin for 7 iron time and time again. Made skytrak look much worse than it is. This bug only shows up for people with tour speed or higher, which is probably less than 5% of Skytrak owners.

[ProTee Max]

Any news or updates on this. It is most certainly a thing. My son can't use 7 iron on TGC2019 any longer, or he will sail the green by 20 yards most of the time. There is something special about this combination. I am guessing that this exact ball speed & trajectory combo puts the ball in a blind spot of some sort. But partially ball imaged ball usually results in random whacked HLA, but this bug only affects total spin, so maybe it is something else, like flawed logic in the image engine. I hope it is because then there is hope it can be fixed.

If you don't know what I am talking about, check out the TXG video with the skytrak. Halved or quartered spin for 7 iron time and time again. Made skytrak look much worse than it is. This bug only shows up for people with tour speed or higher, which is probably less than 5% of Skytrak owners.

Hi Morini,

Could you have a try playing with the " High BackSpin Correction" turned OFF in the SkyTrak TGC Settings?
Open the txt file and change it to OFF; Save the file and restart the computer.


Thank you

[Morini]

Could you have a try playing with the " High BackSpin Correction" turned OFF in the SkyTrak TGC Settings?
Open the txt file and change it to OFF; Save the file and restart the computer.

Thanks, I will give it a shot ... but I don't think it is TGC2019 specific, and exists for Skytrak range as well. It is just that it is much more frustrating to sail a green in a sim than on Skytrak range.

[Morini]

Well almost 3 years on since Hankydisplasia and myself posted about it, it appears to fix is in. 4.4.6 has the following:

• Fixed High-Speed 7/8 Iron Spin Bug

I believe Hankydisplasia has long since moved on, and my son is off to college. I don't hit fast enough to trigger this issue so I can't test it. I hope the small percentage of Skytrak OG users with 130+ ball speed 7 iron sim golfers will appreciate having this bug finally squashed.

TXG should re-visit their review, but given that the OG is now in death spiral, I doubt they will bother. Here is a link the the review where this issue is glaringly obvious:

https://www.youtube.com/watch?v=17ICvO80dFQ

[hankydysplasia]

I believe Hankydisplasia has long since moved on, and my son is off to college. I don't hit fast enough to trigger this issue so I can't test it. I hope the small percentage of Skytrak OG users with 130+ ball speed 7 iron sim golfers will appreciate having this bug finally squashed.

I have played about 6-8 rounds since this, and have not had a single misread with my 7 iron. This seems to have worked! I'm still on the OG Skytrak.

[Morini]

That is great news. Your diligence got the ball rolling. I don't think they ever acknowledged it. Did Rodgeric ever get back to you? We will probably never know, but I wonder what the cause is. I am curious whether there are "blindspots" in the images and if the fix simply used logic as a kludge ... basically override results when these ball speeds and VLA show up. Or maybe the images were fine, and there was a small window where the image engine had a flaw that could be easily fixed.

I am also curious to what degree Skytrak spin calculations rely on calculations vs measurment. I had always assumed 100% the latter, but maybe it relies at least in part on (very good) guessing.

I also wonder if the opposite issue is also fixed ... or maybe more common now. The one where high slow drives get tripled spin.