Average carry calculated based on multiple clubs. Why?

[sroest]

I noticed that the value of average carry displayed on the driving range screen (not in the shot history screen) in the Skytrak practice mode (iPad version 2.6.5) is calculated based on the carry of all shots hit in the current session. So If you hit for example 10 shots with your pitching wedge (and your average carry is 100 yards) and start hitting your driver, your average carry is also calculated using those 10 pw shots. That makes no sense to me. Why not calculate your average carry based on the shots you only hit with the club you hit now?

btw, before hitting a different club, I select the club with the button in the middle.

[doublebogey]

You need to select the club you're hitting with (it's the button in the middle at bottom of screen).

[Lgnir]

Doublebogey is correct. As long as you are selecting the club you are hitting on the driving range, you will have separate carry/total distances for each club displayed

[sroest]

I forgot to mention that I always select the club I am hitting. Are you guys using version 2.6.5. on the iPad? Maybe there is a difference in functionality between the iPad and PC version?

@lgnir: I am not referring to the displayed total and carry distances, but to the calculation of the average carry distance.

can anyone using an iPad verify if the average carry is calculated based on multiple clubs (i.e. Pw, 5i, driver)?

[teamacacia]

sroest , I just did the following range session on the driving range: 54*, PW, 8i, 6i, Driver#1, Driver#2.
To start, I always go into the session settings and make sure carry distance is displayed rather than total distance.
I initially started out hitting the 54 (avg carry 105) and PW (avg carry 125) without any specified practice greens and felt like it was displaying the collective average of the two clubs. About mid-way through the PW, I added a practice green at 125 yd, and it appeared to cause the averages to then split per club as my avg immediately jumped from the 110's to 120's. I was hitting 10 shots per club.
I moved the practice greens back as I progressed up through the 8i & 6i. The displayed avg carry also stayed true to the club.
I deleted the practice green for the two driver tests. I hit them near identical so I cannot say if they averaged together or separately. I was also getting hassled by the 90 degree garage temps and the kiddo to come in and play so I kinda rushed through that part.

In the end, I'd recommend to try adding a practice green for each club as it seems that the practice green's presence seems to alleviate the avg carry issue.

[sroest]

teamacacia, I did a Skytrak session this morning with different clubs. Whatever I tried with using practice greens and changing practice green settings, the average carry distance was calculated based on all clubs hit. After every shot I switched from the main driving range screen to the shot history screen and average carry on the main screen differs from the shot history average carry value as soon as you have changed the club you are hitting in the main screen and have hit a shot with it.

[teamacacia]

sroest, Well crud, that is disappointing. I will see if I can do another test after work again and check after every shot as you did.

[gibbiesmalls]

I also only get the avg of all shots taken. I could select one club after another, and the average yardages displayed always includes all shots taken. Annoying to go from lob wedge to 4 iron and not be able to get my 4 iron averages carry without also including all my LW shots.

All of this in practice (range) mode. All my data is saved accurately on the 360 site or on the shot history section, but the main display page (range mode) never zeros out after selecting a new club.

[YonexMan]

I've already mentioned this problem/bug to Seth. The average carry distance on the practice range is meant to only reflect the current club you are using, not all clubs. In older versions of skytrak, the average carry was only calculated on the current club. Current version for some reason a bug came in. Seth is getting this fixed in the next update.

[sroest]

Thanks! Let's hope this bug is fixed in the next release.

[SkyTrak_Seth]

Thanks for bringing this to my attention, guys. This must be a regression bug, but I will make sure it's taken care of in the next release.