Last updated: August 30, 2026
A 30 to 40 yard gap between your simulator and the course is almost never one big lie. It is usually two or three honest 10 yard gaps stacking: a modeling gap (how the software extrapolates flight), a strike gap (what the mat hides), and a baseline gap (whether your "real" number was ever real). Isolate each one and you fix the right thing.
Because you are comparing a modeled carry number against a remembered total that may have been padded at the source. The simulator is not necessarily wrong. Your baseline might not be right either. The truth usually lives somewhere between them, split across three independent gaps that can each contribute an honest 5 or 10 yards.
I run a Uneekor Eye Mini Lite into GSPro in my garage. When I finally tested my outdoor carries with measured ten ball blocks, my course numbers ran shorter than my sim numbers, not longer. The culprit was low point issues that a mat had been hiding, plus a yardage card that had quietly gone stale while my swing changed. Diagnosing the gap started with admitting I had more than one problem.
Every distance discrepancy between indoor and outdoor lives in one or more of these three buckets. Naming them is the first step to fixing the right one.
Indoors, your launch monitor sees a short slice of ball flight and models the rest. Every unit does this differently, but every unit does it. The model takes your measured launch angle, ball speed, and spin (measured or calculated) and simulates a full trajectory through air. That simulation is where carry distance comes from.
Modeling error compounds with hang time. A wedge flies a short, steep arc, so the model has little room to diverge from reality before the ball lands. A driver hangs in the air far longer on a shallow arc, which gives the model more time to accumulate small errors in spin rate, launch angle, and drag. That is why short irons tend to agree between rooms while the driver is where the gap shows up.
A hitting mat is more forgiving than turf on a heavy strike. When you hit slightly fat off a mat, the club skids across the surface into the ball. You still get a number worth writing down. The same swing off grass is a chunk that goes nowhere.
This means on mis hits a mat reads longer than the equivalent grass strike, not shorter. The mat itself cannot subtract yards from your indoor numbers. If your outdoor distances are shorter than your sim, the mat is not the cause. More likely, the mat has been flattering your strike quality indoors, and turf is exposing what was always there.
This gap makes the course shorter than the sim. A ten ball block outdoors, especially off turf, will include the 2 or 3 heavy strikes that a mat would have rescued. Your outdoor average drops. Your sim average stays high because those same swings still produced usable ball speeds off the mat.
The number you call your "real" distance usually came off a machine too, so the comparison is one sim grading another. Three common ways a baseline stops being a measurement:
When a padded baseline meets a conservative sim model, you can manufacture a 30 yard gap out of nothing more than two 15 yard accounting errors.
Understanding what is measured versus what is modeled helps you know where to trust your unit and where to be skeptical.
| Technology | Ball speed | Launch angle | Spin rate | Carry distance | Club delivery |
|---|---|---|---|---|---|
| Radar (Trackman, FlightScope Mevo Plus) | Measured | Measured | Measured (outdoors); extrapolated with short indoor flight | Modeled indoors (tracked outdoors with enough flight) | Measured on Trackman; the base Mevo Plus measures attack angle and spin loft, while path and face need the Pro Package |
| Photometric/camera (Uneekor, GCQuad, Bushnell Launch Pro) | Measured | Measured | Measured (from ball markings or high speed images) | Modeled (flight model output) | Measured where enabled; on several units it is a paid unlock or needs club stickers |
| Budget portables (Garmin R10 radar, Rapsodo MLM2Pro) | Measured | Measured | Calculated (the R10 models it; the MLM2Pro needs marked RPT balls for measured spin) | Modeled (downstream of calculated spin) | Estimated or omitted |
Whether club delivery data (club path, face angle, angle of attack) is measured, estimated, or a paid unlock varies unit by unit, even within a technology. The free accuracy guide breaks it down device by device.
There is humility available on both sides of the radar versus camera debate. Radar units track real flight and are happiest outdoors; indoors they extrapolate because the ball hits the screen before the trajectory completes. Photometric units measure the launch window precisely indoors, but everything downstream of launch (carry, total, descent angle, apex) is a flight model output, not an observation. Both technologies model carry. Neither is lying. Both can be wrong.
These tests are free, require no special equipment beyond your existing setup, and isolate each gap independently. Run them in order because each one narrows what the next one needs to test.
Before you decide your simulator is lying, make sure your expectations are calibrated. These are well struck bands anchored to Trackman tour average data, meaning the window a solid strike lands in for its club, not a target every swing should hit.
| Metric | Driver | 7 iron | Pitching wedge |
|---|---|---|---|
| Smash factor | 1.45 to 1.50 (1.50 ceiling) | ~1.33 | 1.18 to 1.25 |
| Backspin (rpm) | 2,000 to 3,000 | 6,000 to 7,500 | 9,000 to 11,500 |
| Descent angle | 33 to 40° | 45 to 50° (holds greens from ~44 to 45°; sub 40° runs out) | 48 to 52°+ |
Well struck bands anchored to Trackman tour average data. A smash factor above 1.40 on a 7 iron usually means a thin or de lofted strike, not a better one. On a simulator, carry is the honest number; total depends on the firmness the software models.
Two free tools can speed up this diagnostic. The launch monitor decoder takes a pasted CSV export and grades your smash factor, spin, launch, and descent against well struck windows for each club, so you can see which numbers deserve your attention. The launch monitor accuracy guide shows what your specific unit measures versus estimates, so you know which columns of your export to trust before you build a yardage card on them.
Both are free, require no account, and work with data from any launch monitor.
Once you know which gap is contributing, the fix depends on the bucket:
Disclosure: I built Fore-ward Thinking and its AI coach Chip so the remembering part of this is not a spreadsheet job. You hand it your launch monitor exports and it keeps your per club history across sessions, coaching from what your numbers actually average instead of the swings you remember, which is exactly how my own stale yardage card finally got caught. I am the founder, and the diagnostic in this article works whether you ever use the app or not.
Can a hitting mat make my simulator numbers read shorter?
No. A mat is more forgiving than turf on a heavy strike. A fat contact off a mat lets the club skid into the ball, so you still get a usable number. The same swing off grass is a chunk. That means on mis hits a mat reads longer than the equivalent grass strike, not shorter. The mat cannot subtract yards from your indoor numbers.
Should I compare carry distance or total distance between indoor and outdoor?
Always carry. Total distance depends on roll, which is a software model influenced by firmness settings, altitude, humidity, and wind in the sim environment. Carry is closer to what the unit actually measured or computed from launch conditions, so it is the more honest comparison point.
Is indoor swing syndrome real?
Yes, and the ball speed test makes it measurable instead of a guess. Some golfers swing more cautiously indoors, producing 3 to 5 mph less ball speed with the same club. On a mid iron that alone is roughly 6 to 10 yards of carry. If your ten ball average ball speed is lower indoors, the unit is honestly reporting a different swing, not a bad read.
Should I adjust the altitude setting until my distances match?
No. Cranking altitude until the carry looks right relabels the number instead of correcting it. You lose the one thing the machine was for: an honest measurement. Set altitude to your actual elevation and let the numbers be what they are. Use the three gap diagnostic to find what is actually different.
Why does the gap get bigger with longer clubs?
Modeling error compounds with hang time. A wedge flies a short, steep arc, so the flight model has little room to diverge from reality before the ball lands. A driver hangs in the air far longer on a shallow arc, which gives the model more time to accumulate small errors in spin rate, launch angle, and drag. That is why short irons tend to agree between rooms while the driver is where the gap shows up.
Keep going:
The R10 calculates spin indoors instead of measuring it, and carry follows the model. The free ten ball speed test that tells you whether the gap is the machine or your strike, the aim check for shots that always read right, and what marked balls actually fix.
A plain English guide to reading the ball and club flight numbers your launch monitor feeds into GSPro, and what "good" looks like club by club.
A measured loop of baseline, work, retest, and log, with beginner, intermediate, and advanced versions and a printable session template.
Clear definitions for every number your monitor reports: smash factor, club path, spin, face to path, angle of attack, and more.