Outstanding videos Ben! Thank you so much for doing this for us. It is incredible what you have achieved and is willing to share with us. Thank you!

@trpl_bgy

5 ай бұрын

My pleasure! I'm glad you enjoy it. I appreciate the compliment.

This is such a great video. I finally have everything set up to load by voice command. This is a complete game changer for the GSPro/ MLM2Pro experience! Thank you for sharing!

@trpl_bgy

5 ай бұрын

Glad it helped!

Great stuff, gonna try it. I've been thinking about using my mlm2pro and sign up for gs pro. This makes it so much easier

Great content. Do you have a video for Mevo+ connector and web putting?

Your hitting mat and putting area looks so slick! Did you make it?

@trpl_bgy

5 ай бұрын

Thank you! I did do the build/install. This space went from garage junk storage to Sim Room in 2023 and it was so fun to build!

wow, you have it working seamlessly. This is my next step. Which hitting mat and green surface do you utilize? The one I bought may be too soft and affecting shot data if I skim the mat behind the ball.

Thanks for another great video. Is there a reason you recommend the Galaxy s6 versus the newer one?

@trpl_bgy

5 ай бұрын

It just happens to be the one I have. I can only imagine the newer more powerful ones would function even better and process even faster.

@schop

5 ай бұрын

@@trpl_bgy thank you! Keep it up!

@schop

5 ай бұрын

@@trpl_bgy do you think the 64gb is big enough or should I go 128gb?

So helpful! I really appreciate the work -- I'm wondering if you've ever ran into trouble with the webcam putting set up? I can't seem to get my connector to find my camera. I can use it for other applications, such as google meet, but not in the connetor. Any ideas?

@trpl_bgy

5 ай бұрын

Scott I hope you got the help you needed. Sorry for the delayed response. I address in newest video. Just go through the ID no.'s starting at 0 and start up the putting. If 0 doesn't work, try 1 and so on until you connect to it. Let me know if still having trouble.

@scottfergu

5 ай бұрын

Worked perfectly! Gracias.

Hi Joe what and where you bought your impact screen and your turf paddings

@trpl_bgy

5 ай бұрын

Next video to be released middle of this week will detail this!

Great video as always, what spotlight are you using?

@trpl_bgy

5 ай бұрын

Thank you! I added a link in the description of this video for you and others. Amazon LED Pin Light

@ToddJones

5 ай бұрын

@@trpl_bgy hey Ben, also, my practice mode does a thing where it shows a few metrics after each shot with a blurred screen behind it, then goes back to the regular practice screen. Does this after every shot. Is that an iOS thing? Or are you able to get rid of that shot previews?

@trpl_bgy

5 ай бұрын

@@ToddJones iOS issue unfortunately. Forces iOS users to use use range mode. Only Samsung device I own, I bought because of that feature 😕

@ToddJones

5 ай бұрын

@@trpl_bgycan you also put the android tablet in the comments

technically you wouldn't need club head speed, right? I think ball only data is enough for GS PRO? but not sure...

@trpl_bgy

23 күн бұрын

Correct! Club head speed is a nice metric and tells story in relation to ball speed. But important one for GSPro and flight data is Ball Speed. 🙂

@trpl_bgy

23 күн бұрын

Springbok has a Bluetooth Direct Connector now. Make sure you watch this video also to see his newest version. Thank you for the comment and like! Bluetooth Upgrade! Easy Setup & Enhanced Features Explained! GSPro Springbok Connector Update! kzread.info/dash/bejne/oapm2K6NpNGpgZc.html

@jim52356

21 күн бұрын

@@trpl_bgy Great thanks for the info! By the way, what screen do you use? Sounds very quiet and looks great. Any general sim tour on youtube?

Ben. My Man. My hero... How do I submit a bug report for this. I can open an issue on github but wasn't sure if that would be correct given it's a beta version.

@trpl_bgy

5 ай бұрын

What's issue?

@gsoundinc

5 ай бұрын

​@@trpl_bgy Two issues. 1 - When the application opens, it starts scrcpy (mirror application) and then immediately fails with an error that the "Pixel Tablet" application is not open, and it happens just a split second before the tablet application is running. Seems like It's just not waiting long enough before the error. If I rerun the connector application after scrcpy is already running, no issues. 2- If the ball speed is between 20.1 and 39.9 (so shorter chip shots) sometimes it reads it as a single digit, either 2 or 3 whichever is the first digit. I use practice mode in the mlm2pro software. I've never noticed this same behavior on 1.01.32 before, and I have not issues with any of the other ROI boxes. Last time it happened, I paused the connector and did some testing. I moved and resized the ROI box and it never corrected unless I went too far with it and isolated just the whole number. Interestingly, if move the ROI box to another number it read that number correctly. Then if move a different ROI box over the the ball speed number, that new box reads the ball speed correctly. Really weird stuff.

@gsoundinc

5 ай бұрын

@@trpl_bgy Two issues. 1- During the startup of the connector application it fails with an error similar to "Pixel Tablet" application is not running, and it fails just before the application is started. Seems like it just needs to wait a few seconds., 2- Ball speed data, and this is isolated to ball speed data, no other ROI's seem to be failing. This happens on short chip shots where the ball speed is between 20.1 and 39.9. It converts the number into either 2 or 3 (example: 32.7 becomes 3). Oddly enough I think every time it's happened it might be when the decimal number is a 7... not 100% sure on that though. I've never noticed this issue on the 1.01.32 version. Last time this happened, I paused the connector and started some diagnostics in the ROI screen. FYI, I'm using practice mode instead of the range. I could NOT make an adjustment to the ROI box that would get it read correctly. So I moved the ROI box to some other metric and it read that number correctly. Then I moved VLA box over to the ball speed, and it read the ball speed correctly. This leads me to some corrective action going with the metric. I found some of the correction functions in the 1.01.32 source code, but none of them could cause this behavior, so I couldn't help with any more diagnostics.