TGC randomly using calculated LA instead of captured?

[kinitex@gmail.com]

I cant figure out why TGC is randomly using calculated launch angle, instead of the vcam captured angle. It seems to be doing this 2-3 shots out of every 10. I'm looking at a perfect ball streak of 20 degrees on the vcam from a 9 iron, yet TGC used a calculated LA of 31.

The only thing of note is that while the vcam screen has a captured LA of 20, it has no red line which I assume is because the calculated LA was used instead...

V_cam_fallback=60

[ProTee United]

TGC is not using random angles. The data is coming from the ProTee Golf Interface.

Run TGC in a small window and place the interface main screen + the v-cam screen on your desktop. The cam screen will display the angle on the top right. On the main screen it will say: Captured Angle or Calculated Angle. When it says calculated, then it might not have been detected correctly or it switched to a fall back mode.

[kinitex@gmail.com]

I didnt mean its using a random number for the LA, I mean it seems to be random which LA angle TGC decides to use whether it be the vcam or calculated. I have vcam fallback set to 60 so wouldnt this mean that the vcam LA should be used 99% of the time, unless it faults and doesnt find the ball streak?

The issue seems to be when the red line doesnt appear in the capture so it thinks it didnt find the streak, yet it displays the correct LA up in the top right box. But because the red line didnt show up, that is when it uses the sensor mat calculated LA which always seems to be at least 10+ degrees higher.

[ProTee United]

Are you on the latest interface release?
http://csc.protee-united.com/hc/en-u...-07g-available

[kinitex@gmail.com]

Yes I am using 3.07g and PT5 method to find ball streak. The times where the red line doesn't appear after a shot in the capture window, if I click re-analyze the red line will appear and it will find the streak no problem. But again the LA seems to be already found in that top right little box but because the red line didn't appear it ignores it and uses a calculated LA instead.

[kinitex@gmail.com]

Here is an example of what im talking about. Notice in the camera screen it has the vertical launch angle of 13 in the top right box, but yet the red line didnt appear in the capture. So TGC used a calculated launch angle of 24 which was way too much for my 7 iron shots, especially this one which I partially bladed.

When I clicked re-analyze on the capture image, it found the streak at 13 degrees perfectly fine. Note that this is one of my shorter ball streaks, most are normally the full length of the capture window but even some of those will have this bug happen as well.

[ProTee United]

This could be a performance issue. Try changing the value: Number_of_iterations=25 to 50 in the settings file. This will allow the camera twice as much time to process the images. 50 is the max value, so no need to try anything higher.

[kinitex@gmail.com]

Ok that seems to have helped tremendously, thank you for the great support. Out of about 200 shots it happened only 3 or 4 times compared to it happening 2-3 times per 10 shots.

Would increasing raster from 1 to 2 help in performance in anyway?
What about changing the camera from RGB32 to RGB24?

[ProTee United]

Leave the raster at 1. I do not recommend fiddling around with camera settings to try to optimize performance.
What will seriously improve performance is running the cameras in 320x240 resolution (which is the default resolution for ProTee). At 640x480 (what you are using) the system will need to process 3x more pixels to detect the angle.

The 2-3 times per 200 shots could also be something else. Maybe the system was not able to find the ball.

Make sure no other programs are running on your computer when using ProTee. Real time virus scanners and Windows auto update will also decrease PC performance.

[Joshua1745]

This started happening to me today for some reason. Same exact thing. Perfect ball streak with correct reading of launch angle in Right upper corner box of V cam of 13. However, the interface sends TGC what I assume is a calculated launch angle of 32. I also noticed no Red line. I tried re-analayze and it drew the red line and gives the same reading of 13 in the upper corner. Did increasing the interactions continue to help your problem. Also, does increasing the iterations increase the delay from the time TGC displays the ball shot.

[ProTee United]

Increase to 40 should help.