MEVO + Overstating Driver Carry Distance

[Jogolf]

MEVO + data from outdoors setting while using on the driving range, local weather conditions set. Drive carry seems to be overstated. Does data below reconcile with how far the carry should be? Ball appears to clear the 250 yard flag, but cannot visually see by exactly how much, still Mevo seems to be overstating the carry distance.

Mid range iron shots appear carry yardage appears spot on.

[StanMI]

Is it possible it's converting the numbers to Pro V1 carry distances vs range balls ??

[Jogolf]

Is it possible it's converting the numbers to Pro V1 carry distances vs range balls ??

I set it to “range ball” on the Mevo. But would you think it would make that much of a difference? The carry yardage is just math based on ball speed etc. Swing speed and ball speed seem in line with game. But the carry yards just seem much further than it should be based on my numbers. I would love the formula that Flightscope uses to calculate carry yards.

Could you expect 298 yard carry based on a 154 MPH ball speed and 2723 spin?

[preludesam]

Yes it is possible. It does add ball speed in the algorithm when using range ball instead of premium. Range balls have low compression and a hard cover for durability. Higher compression balls (premium) directly correlate to increased ball speeds. It also factors in environmentals and since you are launching it very high at 15 degrees with increased spin it’s assuming you are going to get a distance boost downwind. The higher you get the ball in a tailwind it massively increases the distance.

[StanMI]

Answers for most of that stuff is way above my pay grade!!

There was a Trackman or Flightscope web site where you could plug in your numbers and it would calculate flight. Don't have a link but it would confirm/correct what you have.

[Jogolf]

Answers for most of that stuff is way above my pay grade!!

There was a Trackman or Flightscope web site where you could plug in your numbers and it would calculate flight. Don't have a link but it would confirm/correct what you have.

Above mine to.! Thanks for the info. This morning I could see better on the range and it was saying 280+ carry and landing past the 265 flag. If I had to guess it’s overstating by 10-15 yards. Close enough. I guess the Alabama 90 degrees is going to produce longer carry

[preludesam]

Weirdly enough increased humidity increase's distance. It reduces the density of the air so the ball has less friction when flying. It’s like half a percent for 0-90% though so not really noticeable but its there none the less…

[Shankz]

This is the link for the Flightscope optimizer https://trajectory.flightscope.com I put the first shot in minus the spin axis because it’s not listed and came up with a carry of 260 yards.

[mlurie31]

My understanding for Mevo+ is that since it is radar based, it isn't using a calculation to determine distance, it should be tracking the ball the entire flight and giving you the ACTUAL yardage. Flightscope has it's own calculator here: https://trajectory.flightscope.com/ According to that, 154 mph ball speed at 11.4 degree launch angle with 2700 rpm spin should be a 245 carry, not a 298. But that is sea-level conditions, no wind. Maybe there is a tail wind? Like I said, since Mevo+ is radar based, it should be tracking the actual flight of the ball, not a prediction based on launch conditions.

[preludesam]

This is incorrect regarding the tracking. I think it only tracks the first 40 yards of flight. If you want full tee to ground tracking you have to purchase an X3 or a TM4.

[Jogolf]

The post about range balls and tailwind be a factor in the algorithm makes a lot of sense and I think the reason for the overstated carry yards. I recall the weather showing like an 8 mph tailwind, which I think was not actually prevalent. So it was those extraneous variables that are causing the algorithm to show a longer drive than I was actually hitting. Thanks!