Compatibility

Simulator export guide

Turn a FlightScope session into one Divot Card.

Use a shot-level FlightScope / Mevo export so DivotData can detect the pattern, show the evidence, assign one practice block, and tell you how to retest the same setup.

Current beta status

FlightScope / Mevo

Beta

Best upload

CSV, spreadsheet

File types

.CSV, .XLSX, .TXT

Confidence boost

Club, carry, offline, launch, spin

Mechanical proof

Needs impact data or coach review

DivotData reads shot rows, not summary screenshots. Missing optional metrics lower confidence instead of breaking the flow.

What to upload

Shot-level data works better than summary reports.

Use a MyFlightScope or FS Golf CSV/spreadsheet export with shot-level ball and club data.

Compatibility note: Metric availability depends on model, package, and setup.

Who this is for

Home simulator golfers who want a practical answer to what changed today and what to practice next.

What improves confidence

Clear club labels, one row per shot, carry or total distance, offline/deviation, launch, spin, shot order, and a matched retest.

Export steps

Prepare the file before you upload.

Use the cleanest export path available. If the source only gives a table, copied rows can still be useful.

  1. 1Finish the session in FS Golf and make sure it syncs to your FlightScope account.
  2. 2Open MyFlightScope in a browser and sign in.
  3. 3Open Data, then choose the FS Mevo Golf or matching device area.
  4. 4Select the session you want to export.
  5. 5Click Export or Export to CSV and save the downloaded file.
  6. 6Return to DivotData and use the upload box at the top of the page.
  7. 7Drop the exported file on the upload box or click Choose files. If your source only shows a table, paste the copied rows into Paste Table Text.

Click-by-click walkthrough

Use FlightScope shot data, with source limits called out.

I found official FlightScope software screenshots that show shot tables and data views, but I did not find an official FlightScope CSV export walkthrough with export-menu screenshots. Treat the export path as lower-confidence until validated with real MyFlightScope or FS Golf files.

  1. 1Official software screenshot

    Finish and sync the session

    Complete the FS Golf or FlightScope session and make sure it syncs to the account you use for review.

    Note: FlightScope's official product pages confirm shot-table and data-review software surfaces, but the public official pages I found do not document a stable CSV click path.

    Official FlightScope FS Golf PC software screenshot showing a shot-data table view.
  2. 2No export screenshot found

    Open the data review surface

    Open MyFlightScope or the FlightScope software review area for the matching device and session.

    Note: If the account offers Export or Export to CSV, use that. If not, use a connected simulator export such as GSPro or paste copied table rows.

    Official FlightScope FS Golf PC software screenshot showing launch-monitor data panels.
  3. 3Choose shot rows

    Export or copy shot rows

    Use any available CSV/spreadsheet export. If only a visible table is available, copy the shot rows instead.

    Note: Do not upload a marketing screenshot or summary image as the main file; DivotData needs rows to calculate evidence and confidence.

    No fixed screenshot

    This screen can vary by device, operating system, or account state. Follow the note and choose the option that produces a CSV or other shot-level table file.

  4. 4Next click: DivotData upload box

    Upload to DivotData

    Return to DivotData, keep the source set to FlightScope, then drop the file or paste the copied rows.

    Note: Expect a source-confidence warning until more official export samples are validated.

    No fixed screenshot

    This screen can vary by device, operating system, or account state. Follow the note and choose the option that produces a CSV or other shot-level table file.

Official source: FlightScope FS Golf PC software. Labels and DivotData notes are written for the upload-to-card workflow.

Expected metrics

Metrics DivotData looks for in FlightScope files.

ClubCarryTotal distanceOffline or deviationLaunch angleSpin rateBall speedClub speedSmash factorLaunch directionCurveClub pathFace angleFace to pathAttack angle

Data quality tips

  • Keep radar alignment consistent across baseline and retest.
  • Use a single target line for comparable sessions.

What this cannot prove alone

  • Some metrics require the matching FlightScope model, Pro Package, and setup.
  • Mobile and web export labels vary by app version.
  • Launch-monitor data can detect patterns, but exact swing mechanics still need richer context, strike data, or coach review.

Sample proof

The upload is only useful if it becomes a focused card.

A Divot Card should show pattern detected, evidence, confidence, likely focus, what not to chase, the practice block, and a matched retest protocol.

Sample Divot Card

Low-right / low-fade pattern

Open

Today's focus

18-minute 8-Iron Reset

A short block that narrows start line first, then checks face control, then checks strike/low point.

18 min
Club8-iron
PatternLow-right fade
ConfidenceMedium · 64/100

Start with

Start-line gate

Start the ball through a narrow target window before judging curve.

Why this card

Data quality

82/100

good beta file

Sample

20 shots

Matched stock 8-irons

Coach-style note

The ball-flight pattern is clear enough to practice, but the exact mechanical cause should stay a hypothesis until a coach or impact evidence validates it.

Get your first card free

Demo card. Launch-monitor data can identify patterns and confidence levels, but it does not prove exact swing mechanics by itself.