Foresight GCQuad and GC3 — CSV export and analysis
Foresight's GCQuad and GC3 are camera-based launch monitors — not radar — used heavily in OEM club-fitting bays. GCQuad lists at $11,999 (on sale from $15,999) directly on Foresight's site; GC3 pricing varies by bundle configuration, so check foresightsports.com for the current price rather than trusting a single number here. ContactCoach parses the CSV format both units produce and adds a free analysis layer on top of Foresight's own camera measurements.
How do I export a CSV from Foresight software?
Foresight's FSX software (2020 or newer) has an auto-export feature: once enabled, it continuously writes shot data to a running shots.CSV file, plus a LastShot.CSV that updates after every single shot — you don't have to manually export a session the way you would on some other monitors. Foresight's own help center covers the exact setup: "How to Save Shots on GCQuad and QuadMAX" and the equivalent GC3 article. Upload the resulting shots.CSV at / and ContactCoach auto-detects the column layout directly — no manual mapping required.
What does a Foresight export include?
Because GCQuad and GC3 use a four-camera "Quadrascopic" photometric system instead of radar, they capture some things no radar-only unit can. Ball data: launch angle, side angle, ball speed, total spin, carry, and side spin/spin axis. Club data: clubhead speed, smash factor, club path, angle of attack, loft/lie, face angle, and — the standout capability — exact impact location on the face and closure rate. Spin comes from actual dimple tracking rather than being inferred from launch conditions, and impact location tells you precisely where on the face you struck the ball, which is why these units are standard equipment in fitting bays.
What does ContactCoach add?
Because Foresight already measures club path and face angle directly, ContactCoach uses those as-is for face-to-path rather than estimating — no D-plane approximation needed when both real values are present. Foresight's own product documentation doesn't confirm whether descent/landing angle ships as a native export field, so if your CSV doesn't include it, ContactCoach fills that one gap:
| ContactCoach adds | Status | Guide |
|---|---|---|
| Descent angle | Estimated only if your export doesn't already include it | How it's estimated |
| Face-to-path | Uses Foresight's measured face angle + club path directly | Reading face-to-path |
| Dispersion ellipses per club | Computed from your visible shots | Reading the ellipses |
| Gap analysis across your bag | Computed from carry percentiles | Reading gap analysis |
| Mishit flagging | Computed from per-club thresholds | How mishits are flagged |
At an $11,999+ price point, the case for ContactCoach isn't measurement — Foresight already measures more than almost anything short of Trackman. It's that FSX doesn't give you per-club dispersion ellipses, gap-overlap warnings, or adaptive mishit flagging across a session the way ContactCoach does, for free.
Measured or modeled — what should I trust?
Trust nearly everything as measured: spin from dimple tracking, exact face impact location, club path, face angle, and ball flight numbers are all camera-captured, not inferred. The one caveat is descent angle, which ContactCoach only estimates (from carry and apex height) when your particular export doesn't already carry a measured landing angle — check your own CSV's columns to know which case you're in, and ContactCoach's app labels the value "estimated" or "measured" accordingly either way.
Try it
Upload your own shots.CSV at /, or click "Explore a sample session" on that page to see dispersion ellipses, gap analysis, and mishit flagging running on real camera-measured data.