How-To

Deep Dive: Webcam Putting in GSPro, From Setup to Working

The busiest topic in our community, and the one that beats the most people. This is the whole path in order: the license switch, the camera, the reading zone, the mask, the light, and the radius setting that decides whether a ten foot putt goes ten feet or a hundred. Built from what members who got it working actually did.

My Sim Setup·Sep 30, 2026·26 min read· 0 views
This is a build-bench deep dive: the detail you want with the camera in your hand, not while shopping. Every step here comes from members who got webcam putting running in their own bays. Where the community never settled a question, this guide says so instead of filling the gap with a guess. A confidently wrong keystroke costs you another evening.

Webcam putting is a camera pointed at the floor, a small piece of software that watches a colored ball roll through a marked box, and a connector that hands the speed and direction it measured to GSPro as a putt. That is the whole idea, and it is cheap. Members here have it running on twenty dollar webcams. The reason it eats entire weekends is that four separate things have to be right at the same time, the license type, the camera, the light, and the ball, and when any one of them is wrong the symptom looks identical: nothing reads, or something reads and your five footer travels a hundred feet. The most common message in our putting channel is some version of "I have watched every video, I have spent hours, I am done." This guide takes the four in the order that stops you chasing the wrong one.

First, check whether you even need it

Webcam putting exists because of a physics problem. A putt only needs two numbers, speed and direction, and both are easy to read from directly above the ball. A radar unit sitting behind you is looking at a ball that never leaves the ground, and members consistently report it guesses direction badly and speed inconsistently. Camera units that sit beside or above the hitting area generally do not have that problem.

So the honest first question is which camp your launch monitor is in. Members running the Mevo Plus family, the Garmin R10 and the Rapsodo MLM2PRO are the ones who end up on a webcam, and long-time owners describe it as the fix that makes those units competitive in putting leagues. Owners of the Square, the Spica, the Uneekor Eye Mini and Lite, and the Garmin R50 after its updates mostly get told the opposite in our channels: use the official connector and let the unit read the putt. If you have a unit that already putts well, adding a webcam is work you do not need.

GSPro connects to one interface at a time. That single fact is behind most failed setups. If GSPro is talking to your launch monitor through its own official connector, there is no second door left for putting data to come through, which is why webcam putting always runs through a third party connector and why the official connector cannot do it. It also matters competitively: members report that cash games and some tours require the official connector and do not accept webcam putting, so check your league rules before you build your bay around it.

The license switch that stops almost everyone

Your GSPro license has to be converted to Open API rather than the manufacturer profile for your launch monitor. This single step is the most repeated answer in the archive. The failure looks like a connector that finds your launch monitor perfectly, then refuses to connect to GSPro and tells you the API is not open. Members have gone back and forth between the Rapsodo profile and Open API, or between the Full Swing profile and Open API, and the connector only works on Open API. You do the conversion in your GSPro account, not in the connector.

Rapsodo MLM2PRO owners carry one extra chore: members have reported having to re-authenticate through a third party page on the Rapsodo side roughly every 24 hours to keep the connector fed. That is one owner’s account rather than a documented requirement, and Rapsodo ships updates, so treat it as a thing to check rather than a step to plan around.

For the connector itself, the Springbok MLM to GSPro connector is what most members here run and what most of the community answers assume. At least two alternatives circulate: one posted on GitHub, and one called Shotbridge, written by a member of this community who is active in the channel. They are not the same program, and the difference that matters day to day is that the Springbok putting window keeps the camera running the whole time, while the alternative can be set to only wake the camera when a putt is called for. That trades a couple of seconds of startup per putt for a camera that does not sit there heating up all round.

Launch order gets asked constantly and the archive does not fully agree. The order repeated most often is: connect the launch monitor, start webcam putting in the connector, then open GSPro and connect. One experienced member argues for opening GSPro first. Both work for the people recommending them, so pick one, write it on the wall, and always do it the same way. What everybody does agree on is that the putting window has to be running before GSPro wants a putt, not started halfway through a round.

The camera: frame rate first, everything else second

Frame rate is the specification that decides whether long putts read. The working floor in the community is 30 fps measured inside the putting window, and the standing advice is to buy a 60 fps camera to get it, because real room lighting drags the actual rate down. Members with 60 fps cameras routinely report 24 to 35 fps in the app. That is fine. A member running a 120 fps camera reports holding about 120 and reading putts cleanly up to 22 mph of ball speed, which is a genuinely useful margin if long putts are where you are struggling.

Watch the resolution trade. Many cheap cameras do 30 fps at 1080p or 60 fps at 720p, not both at once, and members have found the putting app quietly defaulting back to the higher resolution after they set it. The fix members landed on is editing the resolution in the config file so the camera actually runs where you want it. Check the frame rate number displayed in the putting view rather than trusting the box the camera came in.

Height above the ball: members land between about 4 and 8 feet, and most who tuned it settled near 6. Mounting too low is a real failure mode, one member had the camera 2 to 3 feet up and could read short putts but not long ones, and going up to around 6 or 7 feet fixed it. Higher is not automatically better. As one member put it, a camera that reads fine at 7 feet can false trigger constantly at 8 if that is past its effective focal distance. A camera with manual focus, manual zoom and a manual aperture gives you a way to fill the frame with your putting lane from a ceiling mount instead of shooting the whole room.

Mounting is wide open. Members run ceiling mounts, brackets clipped to the projector mount, plain tripods next to the putting mat, and 3D printed housings. The line that matters is not where you hang it but that it is square to the line you putt on. There is no setting for rotating the reading line, the creator of the app confirmed to a member that you rotate the physical camera, which is easy enough once you know to stop hunting for the menu.

The run back to the PC is a real constraint. A ceiling or projector mount is usually 15 to 35 feet of cable, and members are clear that a passive extension costs you frame rate. Use an active USB 3.0 extension with its own power, which is what the long-run members recommend. One member who moved to a powered USB-over-ethernet extender went from roughly half the camera rated frame rate to the full rate on the same hardware. Wireless is the one route the archive says does not work: a member tried a wireless streaming camera and an OBS virtual camera and got a black screen at 2 fps, and only got it working by plugging the camera in as a plain USB webcam.

One program at a time can own a webcam. If OBS has the camera, the putting connector will not get it, and vice versa. This bites members who add a streaming camera or a swing camera later and suddenly cannot putt. It also means the camera index can shift when you add or move USB devices, which shows up as the putting window opening on the wrong camera or on nothing at all.

Where you putt from, and the lip that ruins it

You do not have to putt from where you hit. This is the single piece of advice that unsticks the most people in the archive, and newcomers almost never know it. Move the putting spot beside your hitting strip, or to the far end of the mat, or to a completely different part of the room, wherever you have a flat, uniform surface with clean roll. Members with wide hitting areas commonly putt from a narrow lane along one side of the strip.

Height mismatches are the usual reason people have to move. A stance mat with a rubber lip that stands above the surrounding turf makes the ball hop as it leaves the mat, which both wrecks your feel for distance and puts a hard edge in the camera view. Members solve it by putting somewhere else rather than by fighting it.

If you are building the floor now, two numbers from the flooring channel save you money later. Set your hitting strip 1/8 to 1/4 inch proud of the surrounding turf, not flush. Members who made it flush report the club traveling further through the turf than they expected and tearing it, one of them by a couple of inches. And for the putting surface itself, the members who care about roll use putting-green turf in the 10 to 11 stimp class with no infill, laid over foam, and use a separate stance mat or strip for full swings because putting turf wears out fast where you stand.

Does putting off a different surface from the one you hit off matter? Not to the camera, and not to the software. What matters is that the roll is smooth, the lighting is even along it, and you know the stimp of the surface you are actually rolling on, which is the next section but one.

📐 Lay out the putting lane in the 3D builder

The reading zone: far smaller than your instinct says

The most common self-inflicted wound in the archive is a reading zone the size of the room. Bigger looks safer and does the opposite: every extra square foot is more floor, more reflections and more shadow for the software to mistake for a ball. Members who resized down repeatedly report an immediate improvement, and the author of one of the connectors puts it plainly, the larger you make it the more variables you add.

Two different sizes are in play and people confuse them. The small start box, where the ball sits before you hit it, only needs to be a few inches front to back, about three or four ball depths, not the two or three feet people leave it at. The read area is the part that needs length: the camera has to see the ball clearly at the start of the roll and at the end of it, and the working figure in the archive is 3 to 5 feet of visible, evenly lit roll. In the connector that asks you to define a measured zone, a member who has tuned one reports a zone of 18.5 inches wide by 62 inches long, and advises 18 to 20 inches by 50 to 60 inches as a starting point.

If your connector asks for the physical dimensions of the zone, measure them with a tape and enter them exactly. The ball detection math uses those numbers to turn pixels into real distance, so a zone that is 20 inches wide and told the app it is 24 will read every putt wrong in a way no other setting can fix. It is a one time job.

Narrowing the zone is also the tidy fix for a light bleeding into the frame. A member with a bright pin light in view could not get a clean read until they pulled the box in tight enough to crop the light out of the tracked area. Which raises the related trap: do not putt through a spotlight. A ball that starts inside a pool of light and rolls out of it is two different colors to the camera, and no slider setting covers both.

Ball color and the mask

The software is not finding a golf ball, it is finding a color. The mask window is where you tell it which color, and the target is unambiguous: the mask should be almost entirely black, with only your ball showing as white. Members regularly tune it backwards, a white field with a black ball, and nothing works until somebody points it out.

Color first. Yellow is the most recommended in our community after side-by-side testing, matte rather than shiny so it does not glare. Orange and red both have committed users with good results. White works but members warn it is a trap: white is everywhere in a sim bay, on shoes, shirts, putters and hats, so you end up enforcing a dress code on yourself and your guests. The right answer depends on your floor color, your putter and what you wear, so buy two or three colors and test rather than copying somebody else.

The method members walk newcomers through: put three or four identical balls along the line you putt on, then slide all the minimum values to the bottom and all the maximums to the top so everything is showing. Bring minimum saturation up first, usually around two thirds of the way, until a usable mask starts to form, then bring the maximum down to meet it, then do the same for hue and finally for value. As you close the gaps more black appears. The moment the white ball starts shrinking or looking ragged, back off slightly. Tight is the goal: loose settings are what cause phantom reads further down the line, where the software sees circles that are not balls and calls your putt finished early.

Never set a minimum higher than its maximum. Hue, saturation and value each have a pair, and crossing them produces a negative range that reads no color at all and can lock or crash the putting window. Members have reinstalled the whole connector chasing this. If the window is already locked up, edit the values back into the config file by hand.

The controls in the Springbok putting window are two keyboard shortcuts, and both are lowercase, which is its own small heartbreak in the archive. Lowercase "a" opens the camera controls and the box coordinates, including exposure. Lowercase "d" opens the mask and the hue, saturation and value sliders. Close each window with the same key you opened it with. Members are firm about this: if you click the X to close it, your settings do not save, and you get to do the whole thing again tomorrow night. Screenshot your slider values once they are good so you can get back to them without experimenting.

Light: consistent beats bright

Ask the channel whether you want more light or less light and the answer that comes back is neither. You want the same light. Same amount, same color, every time you play. A mask tuned at 8pm under one lamp is a mask that fails at noon with the garage door open, and members chasing settings that "will not save" are often actually chasing changing daylight.

Make the 3 to 5 feet the ball rolls through evenly lit end to end. Uneven light along the path is the specific cause of long putts dying halfway: the ball is the right color at the start and a different color at the far end. Turn off auto exposure and any automatic adjustment in the camera companion software, because a camera that helpfully rebalances itself mid-round will move you off your tuned mask. Members also report brightness settings refusing to stick, and the answers that worked were setting it in the config file, setting Windows to let the app control the camera, and turning off the camera maker’s own auto features.

For garages and rooms with windows, the community fix is blocking the daylight rather than out-lighting it: blackout film on the glass, blackout curtains, or moving blankets held up with spring clamps for an easy take-down. For added light, members use a small soft light mounted beside the camera, a dimmable one so they can add a little without washing out the projector image. A second cheap projector aimed at the floor is a popular two-for-one, it lights the putting area and draws your aim line at the same time, and members have wired it to switch scenes automatically when GSPro shows the putter is in hand.

Keep a short known-good note: camera height, frame rate, the hue, saturation and value numbers, your radius, and your stimp. When something drifts, and it will the first time the light changes or you move the camera, you have a baseline to return to instead of starting over. Members who moved a camera a few feet after months of clean putting describe having to retune from scratch because the light was different in the new spot.

Radius: why your five footer went a hundred feet

If your reads are clean but the speed is nonsense, the setting you want is radius, and it is the most frequently missed control in the whole archive. Radius tells the software how big the ball is in the camera view, which is how it converts pixels of movement into real speed. Because of that it works backwards from how it reads: a bigger radius number makes the ball roll slower, a smaller one makes it faster. Members have set it to 1, watched a five foot putt travel over a hundred feet, and concluded the whole thing was broken.

The putting window suggests a radius when it starts up. That suggestion is usually right or within one either way, so try the number it gives you, then that number plus one and minus one. Do not copy somebody else’s value from a chat message. Radius depends entirely on your camera height and zoom, and members report working values from the low single digits to the mid twenties on setups that are all working correctly.

The calibration loop members use, in order. One: find out the stimp of the surface you actually putt on, which is usually printed on the turf spec or can be measured the same way you would stimp a real green. Two: set GSPro to that same stimp. Three: set up a ten foot putt in GSPro, on a flat green, and adjust the radius until a putt that rolls ten feet in your room also rolls ten feet on the screen. Then test it long, out to 40 feet or so. A member who did exactly this reports it holding true all the way out.

Separately from radius, the Springbok window has a camera window width setting, which only changes how big the putting view is drawn on your display. The default is 640. Members shrink it to around 150 to tuck it out of the way on the GSPro screen, or push it up past 1500 when they are projecting the putting view onto the floor. It has nothing to do with speed. You cannot rotate that window, and the only workaround members found is putting it on a second display and rotating that display in Windows.

Green speed, and why putts still feel wrong

Plenty of members finish the setup, get clean reads and accurate speeds, and still feel like the putting is off. Almost always it is a stimp mismatch. A course in GSPro may default to 8 or 9, while league and tour rounds commonly run 11 and occasionally 12, and at 12 the downhillers get genuinely nasty. If you calibrated your radius against a 9 and then play a league at 11, your feel is wrong before you start.

The fix is to know the true stimp of your own surface, calibrate at that number, and then accept that anything faster on screen is a real adjustment you have to make, not a bug. Members who do this report their sim feel transferring to real greens at a similar speed. Members who never established their surface stimp are the ones who say sim putting never feels like the real thing.

The community also maintains ball-speed-to-distance charts for GSPro at various stimps, and members tested and published the speeds where a putt starts skipping over the hole rather than dropping. They are worth having if you want to putt to a number instead of by feel, with two caveats members are clear about: the charts are for dead flat putts, so slope is still yours to read, and they describe GSPro, not real grass, where grain and moisture do things the sim does not model.

Aiming, and the pointer that will not stay put

Two aiming complaints run through the archive and it is worth being straight about them. The first is that moving your aim means clicking the screen with a mouse, which is awkward from a putting stance across the room. The second is uglier: members report that after every shot the mouse pointer resets to a corner of the screen, so they have to click back into the GSPro window before aim will move at all. Nobody in the archive ever posted a fix for that one.

What members do instead is get off the mouse. The arrow keys nudge aim in small increments, which is what you want on a putt anyway. A control box handles most aiming for the members who own one, and a wireless keyboard is the cheap stand-in. A touchscreen mounted near the bay is popular for menus, starting rounds and aiming off the tee, though members who own both say putting is the one thing a touchscreen is bad at. A couple of members have written their own on-screen button panels to cover the gap. If you are still planning your bay, plan a way to aim that is not walking to the PC between putts.

When it breaks: the short list

The mask is all black and nothing reads

Check you are on the right camera input first. If you cannot see your actual floor in the camera view, no slider setting will help you. After that, check that a minimum value has not been pushed above its matching maximum, and check you have not tuned the mask inside out.

Pressing d closes or crashes the putting window

Use lowercase. Then run the connector as administrator, which fixed it for several members. If it still crashes, a clean uninstall and reinstall repaired it for more than one member, and one member solved a persistent crash by installing the previous version of the connector instead of the newest.

Settings will not save

Close each settings window with the same key that opened it, not the X. You should see it confirm the save. Then look at whether your lighting changed between sessions, which produces the same feeling of settings not sticking. For camera brightness specifically, set it in the config file and turn off the camera software’s automatic adjustments.

Short putts read, long putts do not

This is the classic three-way: frame rate too low, light uneven at the far end of the roll, or the mask too loose so something down the line reads as a ball and ends the putt early. Lay extra balls along the path and confirm every one of them reads before you touch anything else.

The ball goes right on screen and straight on the floor

The camera is not square to your line. Rotate the physical camera rather than looking for a setting. If the read is genuinely mirrored, check the flip or mirror option, and if you are feeding a floor projector, check the projector is in the correct ceiling or floor mount mode.

The putt reads in the connector but GSPro does nothing

Confirm webcam putting is actually switched on in the connector and that it was running before GSPro asked for a putt. Then confirm the license is on Open API. This pair covers almost every instance in the archive.

It works for an hour and then dies

A connector that leaves the camera running all round can cook it. Members hit this at roughly the one hour mark. Either switch to a connector that only runs the camera when a putt is called for, or look at the USB run, since one member traced repeated crashes to a loose connection in a USB port and fixed it by swapping ports.

A phantom shot fires off the tee

Open the mask window and watch it while you move around. Members have found a stray reflection flashing white in the mask, in one case an overhead light catching a pair of white socks, and the software counting it as a ball. Tighten the sliders until the flashes stop.

The connector cannot find the camera any more

Something else grabbed it, or the camera index moved. This usually happens right after you add a monitor, a swing camera or a streaming camera. Close anything else that uses a camera, try the next camera number in the settings, and check the stream format is set to MJPEG rather than still image.

What changes by launch monitor

Mevo Plus and the FS Golf family, including the Gen 2 and the X3: this is the classic webcam putting customer, and long-time owners say plainly that the built-in putting will not be competitive. Setup is the same across the FS Golf units because the connector reads the same app. One gotcha members flagged: if you use the chipping mode toggle in the FS Golf app for short shots, you have to switch it back to full swing afterwards or your next full shot is a free mulligan for everyone watching. A member built an automation to flip it for you and shared it in the channel.

Rapsodo MLM2PRO: Springbok, license on Open API, and the extra re-authentication noted earlier. Members run it successfully, including in league play. Garmin R10: the same path, Springbok plus Open API, and R10 owners are some of the happiest webcam putting users in the archive because it turns a budget unit into one that can play full-putting league rounds. Garmin R50: it putts on its own and members are regularly told to just use the official connector.

Square: putting and chipping work natively with GSPro, no webcam and no extra subscription, which is exactly why members recommend it to people who want putting without a project. Two setup notes from the Square channel: place the alignment stick roughly 16 inches, about 40cm, directly in front of the unit rather than where you would put the ball for a shot, and keep the lens clean, because a fingerprint over the camera was the cause of a long run of missed reads for one member. Spica 3: reads putts from its own optics, and the hitting area is wide enough that members putt from beside the strip.

Uneekor Eye Mini and Eye Mini Lite: putting is good enough that members choose them partly for it, and firmware updates have specifically targeted putting mode. If you are ceiling mounted with an overhead unit, check whether your calibration lets you define a separate putting area rather than one combined box. GC3 and the Bushnell unit that shares its hardware: members disagree in the archive about whether putting is a built-in feature, and it is worth noting that disagreement rather than papering over it. What they agree on in practice is that in GSPro the unit switches to a putt when you are on the green and reads it for most people. When it does not, the putter is often the cause, and members with white, gray or insert putters fixed missed reads with a small piece of black tape on the side of the putter that faces the unit. Take it off before any real competition.

Two setups the community has never actually solved, said plainly so you do not spend a weekend finding out the hard way. SkyTrak Plus through OpenSky: a member asked whether webcam putting can run alongside it and never got an answer, and the author of one of the connectors said later that no testing has been done on SkyTrak and its viability cannot be confirmed. Full Swing Kit: members have got a connector to putt, but the club selection does not follow between GSPro and the Full Swing app, and changing clubs in the app fires a shot in GSPro. There is no working recipe in the archive. A purpose-built integration was still being built the last time it came up.

🎯 Compare launch monitors, including the ones that putt on their own

Get it done in one sitting

In order: convert the license to Open API. Mount the camera 4 to 8 feet over the ball, square to your line, on an active USB run. Get 30 fps or better showing in the putting window. Pick a flat lane to putt on, beside the strip if you have to. Pull the reading zone in tight and light the 3 to 5 feet of roll evenly. Tune the mask to black with one white ball, using several balls down the line, and close the windows with the keys that opened them. Then set the radius so ten feet in your room is ten feet on the screen at your surface stimp. That is the whole job, and it is one evening if you do it in that order instead of the order the frustration suggests.

You are not the first person to lose a weekend to this, and the members who got it working almost all got the last 10 percent from somebody screen-sharing with them for twenty minutes. If you are stuck, post a photo of your camera view, your mask window and your slider values. Those three images are what experienced members ask for every single time, and they are usually enough to spot the problem without you saying a word.
🛒 Compare turf, mats and the rest of the bay
🤖 Get a build plan for your room
Back to the DIY Build Guide
Ready to plan your sim? Walk through every component with live pricing and a 3D room preview.
Start Your Build