Improvements to Putting -- Mevo+ v.18

[JakeGeezy]

I've consistently had issues with putting on all firmwares with the exception of v.12. I've recently upgraded to v.18 and had the same issues (no reads, putts going nowhere). However, the rest of the improvements (chipping, irons etc.) were so good on v.18 that I buckled down and tried to find some solution for the putting. After 3 weeks of working with Flightscope (who were great, but provided no help) I finally came up with a setup that makes putting work great. Sharing below in case it can help other people.

-Alignment is more critical than in prior softwares. I mapped out the straight line from FS Golf on my floor and putted directly on it towards "straight"
-Increased Stimp to an 8 in the TGC Settings (Notepad app)
-Increased green speed to 3 in the TGC Settings (Notepad app)
- Putt from 4 feet from the M+
-Very short follow-through on all putts

No-reads decreased to maybe 20%, and speed was very accurate.

Hope this helps those of you that were hesitant to jump to v.18 or having issues with v.18

[Love2Golf]

Thanks for the testing and tips. I'm having trouble getting the putting to work as well and just resorted to the computer auto-putting for me.

Question - when you adjusted the stimp and green speed did that affect your ability to keep the ball on the green with your approach shots? I already struggle with getting the ball to stay on the green - either rolling off the back or on some sloped greens rolling off the side into the fringe. Then I get the fun of the short/delicate green side chip.

[JakeGeezy]

I was hesitant to adjust stimp for the same reason but I actually haven’t noticed a difference on greens being able to hold. You can also adjust softness of the greens to hold more, independently of speed

[tinker812]

being lazy and not wanting to grab a putter after a chip shot, i have used SW and bladed it to putt on the green. mevo tends to read those quite well, probably because the "putter" head never hides the ball. worth a try if you have to putt, but can't get reliable readings. could also try a different putter or stroke

[JakeGeezy]

One thing I learned through this is that m+ doesn't have any issues with the ball being hidden behind the putter. The m+ is coded to look at objects that are a certain size (ie size of a golf ball)

[tinker812]

then why do moving things like ceiling fans or even projector fans interfere??

[JakeGeezy]

I think they’re working on making those objects have less of an impact by honing in on the size of the projectile. Could be that those items have some moving parts at that size (ie center of the fan).

[JayJo13]

I've consistently had issues with putting on all firmwares with the exception of v.12. I've recently upgraded to v.18 and had the same issues (no reads, putts going nowhere). However, the rest of the improvements (chipping, irons etc.) were so good on v.18 that I buckled down and tried to find some solution for the putting. After 3 weeks of working with Flightscope (who were great, but provided no help) I finally came up with a setup that makes putting work great. Sharing below in case it can help other people.

-Alignment is more critical than in prior softwares. I mapped out the straight line from FS Golf on my floor and putted directly on it towards "straight"
-Increased Stimp to an 8 in the TGC Settings (Notepad app)
-Increased green speed to 3 in the TGC Settings (Notepad app)
- Putt from 4 feet from the M+
-Very short follow-through on all putts

No-reads decreased to maybe 20%, and speed was very accurate.

Hope this helps those of you that were hesitant to jump to v.18 or having issues with v.18

JakeGeezy - The main issue I was having with 0.18 that I don't have at all with 0.12 is sometimes putts launch and go way further than they should. Like a 12 or 15 foot putt launches and goes 50 or 60 feet. It happened enough (several times in a round) that it forced me to go back to 0.12, even though the chipping and iron play was better. Did you have that happen to you and were you able to fix it?

[JakeGeezy]

I did and heres my theory on that: the m+ was reading the "long" putts correctly. We were getting used to hitting it harder than we were on .12 so that the incorrect (but way more frequent) reading of a "short" putt went further. If that's correct, then adjusting the stimp meter allows those incorrect readings to be playable, which is not a bad thing if its consistent.

Also, as a strange coincidence (maybe) I found that if the stimp was higher, the m+ read more consistently and so I've had less of those "long" putt misreads.

[JayJo13]

Thanks for the info. I'll give 0.18 another run with your recommended settings. Hopefully I can get it to work. Cheers.

[JakeGeezy]

I forgot to add that I have Fast Putting set on a crazy high number (like 350 feet) to make it effectively useless