Mevo+ chipping not working

[teridd]

Using my Mevo+ with MLM2PRO-GSPro-Connector v1.04.20 and FS Golf PC v25.3.12.0, and I got both full shots and webcam putting to work flawlessly. The problem is chipping around the green 1-14 yards from the pin. The chips will not register on the Mevo+ unless I hit it hard, then causing it to fly across the green.
I have seen the same problem mentioned on golf simulator forums around the web, but no solutions.
If I convert back to using the Flightscope License instead of the Open API license, the chipping works totally fine in GSPro.
Is there perhaps a setting in the FS Golf PC app I am missing?

[wonder99]

I don't have much experience with FS golf, but I suspect that GSPRO informs FS Golf through their custom connector that a chip or putt is coming. That switches a mode in the Mevo for better accuracy. With this connector (and using OpenAPI) there's no way we can change the FS Golf mode automatically. We could detect the distance to pin, or that a putter is selected, but can't change anything in FS Golf.

…

On Wed, Dec 17, 2025 at 11:55 AM teridd ***@***.***> wrote: *teridd* created an issue (springbok/MLM2PRO-GSPro-Connector#249) <#249> Using my Mevo+ with MLM2PRO-GSPro-Connector v1.04.20 and FS Golf PC v25.3.12.0, and I got both full shots and webcam putting to work flawlessly. The problem is chipping around the green 1-14 yards from the pin. The chips will not register on the Mevo+ unless I hit it hard, then causing it to fly across the green. I have seen the same problem mentioned on golf simulator forums around the web, but no solutions. If I convert back to using the Flightscope License instead of the Open API license, the chipping works totally fine in GSPro. Is there perhaps a setting in the FS Golf PC app I am missing? — Reply to this email directly, view it on GitHub <#249>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIZTO6AVPNKTTG5BIOZRXD4CGDJDAVCNFSM6AAAAACPKXDFZGVHI2DSMVQWIX3LMV43ASLTON2WKOZTG4ZTSNRYGM2TSMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[teridd]

I had a conversation with ChatGPT, and the answers I got make sense, unfortunately.

FS Golf PC drops chips because:
FS Golf PC is not a raw data passthrough.
It enforces hard-coded validation thresholds:
minimum ball speed
minimum radar track time
minimum vertical separation
internal consistency checks

If a chip fails those checks:
it is deleted
no OpenAPI event is generated
nothing can be sent to GSPro

To make chips work:

chip slightly harder
use PW instead of LW
increase ball-to-screen distance
use RCT balls or metallic dots
accept that very short chips may never register

So, it is difficult to use the Open Api with the Mevo+ if you want reliable chipping in GSPro, as the FS Golf PC software will filter away most chips so they never reach the GSPro.