4.2 Update - distances maybe even worse than before?

Received the latest R10 update and was excited to test it out so I used my standard outdoor setup that has a golf net 10' from the shot area and the R10 7' behind it. I've use this exact setup since spring and am familiar with my distances and stats.

The release notes indicate better head speed measurements with this update, so I figured it would give more accurate distances. Shockingly, the numbers are possibly worse than before.

On the course, my driver gives 210-230 carry, with most drives rolling out 230-260. Using the Garmin Golf sim with the 4.2 update, not a single drive carried 200yds. Most were 180-195.

I also use E6 golf and increase my altitude setting to give better distances, and even it was coming up short compared to previous E6 sessions. 

I also looked at the head speed numbers for various clubs and they were all down 10%. Driver was showing in the mid to high 80's and ball speed never getting above 130mph. A MeVo device and a cheap head speed radar show head speeds in the 95-100 range with ball speeds in the high 130's to 140's. 

So basically, everything with 4.2 is as it was before. Maybe worse because previously with Garmin Golf, it would sometimes show a drives with up to about 210 carry.

Garmin - you've really got to give us an option to calibrate to our real playing conditions. Numerous others have requested this. At the simplest level, let us set a % change for the head speed. This simple option would eliminate our biggest complaint in a manner that's trivially easy to implement and use.

Until then, I'll just keep using E6 and setting my altitude to 4,000 to 6,000 feet. That seems to give me simulations that closely match my playing experience where I am, near sea level.

  • That's sad you would think they would compare it to some high end LM to verify the results. Another problem mine isn't updating connect and run Garmin Express and it says I'm up to date 4.0. Haven't been able to figure out how they roll it out guess I'm not on the list yet. Maybe better to not let it update until they get it right.

  • Maybe better to not let it update until they get it right.

    Exactly why I mentioned Risk Mitigation when holding back at 20% for release. We're effectively testing for broader usage. If experience is similar to most, then we're getting another release.

  • It's quite clear that a club head speed in the mid to high 80's will result in a carry distance of approx 170-190 yards.

    This is my normal swing speed, and my normal carry.

    So the big question here is if the unit after the update reads the swing speed correctly?

    Did You compare the swing speed with the MeVo device on the same shots?

    I will do some testing when I get my almostgolf balls, as I currently don't dare to hit real balls in my back yard.

    I have a prgr I can compare with.

    Will not update the unit before I have made some "before" shots, and I will compare again after updating.

    And I fully agree that it should be possible with a calibration factor for each club.

    Not necessarily the club head speed, which I assume the R10 reads correct, but more increase ball speed to compensate for practice balls.

    That is effectively what You do in E6 when changing altitude.

    Your club speed is the same, but ball will travel further due to lower air resistance. 

  • I haven't tried the simultaneous MeVo measurement but should. I was thinking that the radars would interfere but I'll give it a shot.

  • The release notes indicate better head speed measurements with this update, so I figured it would give more accurate distances. Shockingly, the numbers are possibly worse than before.

    Club speed has no impact on distance. Carry distance is impacted by ball speed, launch angle, and calculated spin. This release didn't affect any of those.

  • Well according to Trackman "More club speed equals more potential distance. In fact, adding 1 mph of club speed can increase your distance by up to 3 yards with the driver."

  • Mine hasn't updated to 4.20 yet. I would say that there are many factors that will produce inaccurate results. I think this has as much to do with garmins issues as their software, although i think their software is the main issue. You need to make sure it is level, and you need to make sure its not too low or high. If it picks up the launch angle differently than what is actually happening, it will measure the distance much different than actual. The net needs to be as far away from you as you can have it so that it can measure the ball as far as possible. Anyway, we had much better luck with Awesome Golf trial, but i really don't want to spend another $350. Really wish Garmin's software was worth something, but we aren't paying for the $10/month to garmin either so we are left with the simple range only atm...

  • To be fair to Godspell, as long as the R10 measures ball speed correctly, club head speed doesen't matter.

    In real life ball speed is a combination of club head speed and compression, so of course ball speed will depend on Your club head speed.

    But the unit can measure the club head speed completely wrong, and still give correct distances as long as the ball speed is measured correctly.

    Of course, if You get 130 mph ball speed with a 20 mph club head speed something is wrong Slight smile

    But if the actual ball speed is 130 mph, then the distance would come out correct, and You could for sure assume the club head speed reading is very wrong.

    The R10 reads both club head speed and ball speed, with the actual ball speed is the factor it uses for calculating distance.

  • Just be aware that Awesome golf calculates ball flight and distances based on exactly the same inputs (from R10), that the Garmin Golf app does.

    So You don't need to be more precise in the set up in order to make it work on Garmin Golf.

    Differences in the output between Awesome Golf / E6 / Garmin Golf are all based on how the measured data are processed in the software.

    So if it works in Awesome Golf, then it should also work in Garmin Golf. Because they receive exactly the same data from the R10 unit.

    So there is probably nothing wrong with the R10 unit, but the Garmin Golf app has some improvement possibilities to put it mildly.

  • That increased distance comes in the form of ball speed, which the R10 is already measuring. I found CHS to be off by about 3 MPH every 5 to 7 swings, but it just throws off smash factor.