ProTee 101 plus setup tips for newbies.

[Maverick]

Frame rate still too high and shutter setting is too low. Both are not anywhere close to my settings. For short chips, the shutter needs to stay open longer so the ball streak can be longer, which will make shot detection easier.

[Bubba22]

I agree. Reduce the frame rate and increase the shutter. Try to get a longer ball streak.

[Cklguy2013]

Thanks to Throttle, Zmax, Bubba22 and Protees assistance I am now able to hit short little chip shots and pitches, I was even able to get up and down from over the 14th green at Muirfield! Thanks so much guys!

[Cklguy2013]

Next Newbie questions... is there some way to zoom in on the map to see how far you have to the green when hitting a little pitch? I would be nice to know on a 20 yard shot that it was say 8 yards to the edge of the green and 12 yards from there to the pin.

Also, can the default club selection be changes, the system is always giving me one more club then I need, for example it will come up with an 8 iron when need to hit a 9 iron.

Thanks again for all the help!

[Bubba22]

Arrow key forward and back is one way. Use mini map and hold left mouse button. That allows you to check yardages anywhere from your ball.

The default club can't be changed. At one point ProTee was trying to develop a club caddy selection settings. New developments may negate the need for this.

[Throttle]

Question on sensor pad shot detection sensitivity. Due to space limitations I am unable to take a driver practice swing a few inches before the sensor pad without occasionally hitting my garage rails in my backswing. The increased height of my stance mat is what is causing this. Full swings over the sensor pad fortunately are fine. If I could make a practice swing over the sensor pad prior to teeing up a ball, it would be a viable solution vs hitting garage rails. The issue with that is that protee often thinks the practice swing is an attempted shot. Is there a setting I can adjust that won't detect a shot unless a real ball is struck? My first thought was to mess with the audio detection sensitivity parameters but I wanted to see if there is a different way to do this.

[Maverick]

That's the only way. Set it to 40 or higher but check and make sure chip shots still get detected. It might also affect your ball speed. When playing online, you can take practice swings over the sensor mat while it's not your turn.

[Cklguy2013]

H cam is messed up..

[Maverick]

Some of CKL's camera settings were somehow set to auto. Can not have any settings on auto.

[Cklguy2013]

Thanks to Zmax's help and HoganWood's patients the problem was resolved.. basically I had messed up a setting when doing some rewiring... So, the goal now is a round with no misreads, at this point I'm still seeing 2 types of misreads. First, about 1 in 10 times with a Driver, the ball moves violently to to the left, and about 1 in 20 times on an approach shot (happened with an 8 iron last night) the ball will fly about 30 yards further then I normally hit it, aside from these occasional misreads, the system is working pretty well, and is quite realistic.

As a general observation, I'm finding with a lack of wind, and flat lies, I'm averaging about 2 strokes less from tee to green then with real golf, however this is being partially offset with slightly more putts..

[Archv6625]

I just tried to set up the Protee in 1/2 finished room - no screen, no platform, just a net and I'm getting some really strange results. I'm using interface 3.02d.

I'm having difficulties with the cameras (well - camera. Only tried the v-cam so far) - the image is WAY too bright. It can't differentiate the ball streak from my pants and that part fails. I did set it to 640x480x60FPS, but had to use protee's instructions to change in the interface file. It wouldn't hold if I changed it in the camera stream. I'm using the light that mmlincoln sent with his system and the lighting track is about 10'4" above the floor which would make the light just under 10' off the floor.

And just a question - do the cameras/sensor pad have issues with usb 3.0 ports?

Next issue is with club head speed. I'm getting some pretty wild readings with my driver - and I'm sure some of it is getting used to hitting indoors I don't think all of it is. I've done the bridgestone ball fitting enough times to know my clubhead speed with a driver is consistently somewhere between 108 and 114, depending on the day. THe first time I set it up, I was getting CHS readings between 116-118, which would be great, but I just don't have that without swinging out of my shoes. I realigned the light/sensor pad and then started to get readings right around 80. I tried with a 5i and was getting readings around 75.

I've gone through and made all of the setting adjustments made on the settings.pgs file.

There's something really basic I've missed, just not sure what it is. Help?

Thanks.

[Maverick]

Please read through this thread and my camera "how to" thread. Sounds like camera gain might be too high but there also might be other factors involved. Make sure to deselect anything camera setting under camera device that is in "Auto".

And always post screen shots of the camera views.

[Maverick]

And btw, if you're going to use a beta interface, you have to use latest 3.03a. 3.02d has issues. See interface updates thread.

[Archv6625]

I went to to 3.03a. The v-cam still looks really strange. I took the gain, brightness and exposure each extreme and didn't see any difference in the result image. The gain was at 0 for this screenshot.

Club speed was good for this round of testing though. Everything was showing a 40+ yard hook (I hit an 8 iron that went 116 yards with 45 yards of hook) so I think there's an alignment issue to, but one problem at a time.

[Bubba22]

Turn your send down from 26 to say 15. Take a screen shot but show one that shows the streak on the bottom captures. That looks like it caught the right launch angle.