# Coming from XFLR5, Flow5 or OpenVSP

The three desktop tools and this site describe a wing with the same handful of numbers, laid out differently. XFLR5 and Flow5 take a table of stations and draw straight lines between them; OpenVSP takes trapezoid segments between cross-sections, which comes to the same thing; the [wing designer](/wing) takes root and tip numbers plus smooth control fields for the two planform edges, the dihedral and the twist. This page maps their fields onto its controls, names the one definition that differs, and says how a section travels between them.


## The field mappings

| Here | XFLR5 / Flow5 | OpenVSP | Note |
|---|---|---|---|
| Half-span (mm) | `y_position` of the last section | `Span` of each segment, summed | Theirs is projected onto y, as here; OpenVSP's `Span` runs along the dihedral line, and its `ProjectedSpan` is the comparable number. |
| Root chord, Tip chord (mm) | `Chord` at the first and last section | `Root_Chord` and `Tip_Chord` of the segment | Lengths here are millimetres. XFLR5 and Flow5 scale by `length_unit_to_meter`; OpenVSP has no length unit at all, so give VSPAERO a matching Re. |
| Sweep (deg) | `xOffset` per section | `Sweep` at `Sweep_Location` | Not the same angle. See the next section. |
| Dihedral (deg), and its control points | `Dihedral` per panel | `Dihedral` per segment | One angle here is a straight line; drag the dihedral field's control points for anything else. Theirs is piecewise linear by construction. |
| Tip twist (deg) and the twist profile | `Twist` per section | `Twist` at `Twist_Location` (default 0.25) | Positive is nose-up in all three; negative here is washout. OpenVSP's sign was checked by running it; check XFLR5's with one section before trusting it. OpenVSP pivots at the chord fraction you set, this site at the quarter chord. |
| Root and tip sections | `Left_Side_FoilName` / `Right_Side_FoilName` per section | one airfoil per cross-section | A section goes across as a `.dat` file, below. Between two sections every tool blends, but not the same way: this site blends at equal x/c, OpenVSP at equal normalised arc length, a difference of about 3.5e-4 chord mid-way between a NACA 2412 and an E387. |
| LE and TE planform control points | more sections, each with a `Chord` and `xOffset` | more cross-sections, or the edge blending modes | A curve here is a table there. Going out, sample stations; coming in, place the control points by eye. |
| TE thickness (mm) | part of each foil | the `TE_Close` setting on the cross-section, not part of a CST airfoil | The site's DAT carries the blunt edge, so a file airfoil needs no setting. |
| Tip rondure | none | end caps (round, extended, pointed) | Different shapes; none of theirs is a planform-tangent curve. |
| Reynolds number, for a wing run | a polar set across Re for every section, computed first | one `ReCref` for the whole aircraft | [Wing analysis](/wing/analyze) computes each station's polar as it runs; nothing has to be prepared. OpenVSP's VSPAERO needs no section polars either; its viscous drag is a skin-friction formula. |

The XFLR5 column was read from strings in `xflr5.exe`, not from its source, so test an import before relying on any detail of it. The Flow5 column comes from its XML reader and an example plane file; the OpenVSP column from its source at 3.55.0, with the sweep, twist, blend and file-airfoil behaviour verified by running it.

## Sweep is the one that differs

Here, **Sweep** is a planform control, not a named angle. It places the tip leading edge at

`x_LE,tip = tan(Sweep) · half-span − ¼ · (root chord − tip chord)`

(`app/wing/wing-types.ts`), and for a straight-edged planform the only chord line swept at exactly that angle is the one at chord fraction −¼: a quarter chord *ahead* of the leading edge. OpenVSP's `Sweep_Location` runs from 0 to 1 and cannot express it; XFLR5 has no sweep angle at all, only the offsets.

What the others call sweep is under **Derived Parameters** on the designer: **Sweep ¼c** and **Sweep LE**, measured off the built planform. To reproduce a wing in OpenVSP, enter Sweep LE at `Sweep_Location` 0 (or Sweep ¼c at 0.25); in XFLR5 or Flow5, set the tip section's `xOffset` to `half-span · tan(Sweep LE)`. Coming the other way, set Sweep here until Derived Parameters shows their angle. An assistant connected through the MCP tools reports the quarter-chord angle when asked for it by name; the `sweep` control it sets is the one above.

## Taking a section across

A section travels as a **Selig `.dat` file** in both directions; [File formats](/docs/file-formats) has what the file holds. Every foil page has a Download DAT button, and the file it writes (151 points, name on the first line) is one all three tools read as it is:

- **XFLR5 and Flow5:** File → Open. XFLR5 needs the foil in the project before a wing can name it; Flow5 can also point a plane file at a `.dat` beside it.
- **OpenVSP:** change the cross-section to a file airfoil and read the `.dat`. The points are stored inside the `.vsp3`, and the section OpenVSP then draws is within 5e-6 chord of what this site draws. Do **not** copy the site's CST weights into an OpenVSP CST airfoil instead: OpenVSP's CST has no leading-edge term, so the same numbers draw a different shape (0.75% chord off on a typical section, 4.6% on an S1223).

Coming back, [Compare](/foil/compare) overlays an uploaded `.dat` against library sections and runs it, and the [Kulfan canvas](/kulfan-canvas) fits one to CST parameters so it can be edited, optimized and put on a wing. OpenVSP exports a Selig `.dat` per section; XFLR5 and Flow5 export the foil from the direct-design view. Each writes its own point count and spacing, which the fit absorbs.

A whole wing travels as geometry, not as a design: STEP or STL out of the designer into OpenVSP's importers or a CAD package, with the control fields baked into the surface. There is no plane-file import or export in either direction today.
