> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/ecosystem/payloads/flux-lidar/beta-flux-desktop-app.md).

# \[Beta] Flux Desktop App

## Flux Desktop App - \[Beta] Quick Start Guide

The Flux Desktop App enables SLAM-like alignment and cross-platform support for Fluxscan files, as well as several other small improvements.

{% embed url="<https://youtu.be/pUIqPO8AGWo>" %}

### New Features/Differences from Flow App

* SLAM-like alignment engine for super sharp scans&#x20;

{% hint style="info" %}
Recommended 32GB RAM or higher. Some large scans may need more than this
{% endhint %}

* Greater OBS file flexibility
  * Can process with only L1/L2 signals, or no OBS file&#x20;
* More CRS flexibility
* Windows, Mac, Linux support
* Full lidar FOV on Flux H1 and O1 variants
  * Points captured from the full 360 degree FOV of the Hesai and Ouster lidars are used in the generated point cloud for better capture of vertical faces and objects.&#x20;
* Flight path flexibility
  * Aircraft path is no longer limited to straight mission tracks. Aircraft can be manually piloted in all directions and still produce scans with the desktop app. This is useful for scanning complex objects, vertical faces, and getting in close around obstacles. &#x20;

### Installing

Currently, the Flux Desktop app is a closed beta program. Reach out to <support@freeflysystems.com> if you are interested in joining.

Check your email for a link to download the app

{% tabs %}
{% tab title="Windows" %}

* Unzip the file
* Navigate to the viewer\_cpp-windows-x64/viewer\_cpp.exe file
* Double click to open it
  * You may need to agree to 'run anyway' to open the program
    {% endtab %}

{% tab title="Mac" %}

* Open the folder, then drag the app in the Applications folder
* Double click the app in the Applications folder
  * You may need to click 'ok' to allow the app to open
    {% endtab %}
    {% endtabs %}

### Processing a Fluxscan

#### Import the file

<img src="https://2546427254-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXREyAKYAeQJ4gfg2SPg%2Fuploads%2FLjjiZTOl9ZidG5MB6iSU%2Funknown.png?alt=media&amp;token=e67f172b-bc99-4fb8-a7e9-b5d22cd7d875" alt="" height="194" width="499">

#### Set the Obs file source and CRS.&#x20;

* If Flux was flown with NTRIP was used, this will be selected by default&#x20;
  \*

  ```
  <img src="/files/7HDLSfEdv1F9cclf2W9a" alt="" height="196" width="516">
  ```

  * You can also use an external base station or CORS file. Ensure you have selected the correct coordinates for the base station point and CRS
  * Unlike the Flow app, Obs files with only L1/L2 signals can be used.&#x20;
  * The Flux Desktop app can also process without a base station file

{% hint style="warning" %}
&#x20;The scan may have a decrease in global/relative accuracy and sharpness compared to using an OBS file
{% endhint %}

#### Device Geometry

* Select the aircraft and isolator type you flew the mission with. This is important for calculating offsets from the GNSS antennas&#x20;

  <img src="https://2546427254-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXREyAKYAeQJ4gfg2SPg%2Fuploads%2FQt2bxbRPPr8CzgJPUaoj%2Funknown.png?alt=media&amp;token=d092fcee-c8ef-4724-8fb6-038e6122c846" alt="" height="295" width="464">

#### Solver&#x20;

* Select the Advanced alignment option, Normal works well in the vast majority of cases
*

```
<img src="/files/Ln3cR54MwCFYj8Wfa2IN" alt="" height="249" width="624">
```

{% hint style="info" %}
The default is to do a Trajectory Solve only, which will not use the SLAM-like alignment feature. We recommend using the Normal advanced alignment
{% endhint %}

#### Project Coordinates

* Set as desired. You don't have to specify a coordinate frame unless you want to
*

```
<img src="/files/G5O489EIL4WLoCZFajOu" alt="" height="151" width="481">
```

#### GCPs

* GCPs can be imported if desired, but are not required

{% hint style="success" %}
GCPs are not used to align the map or modify the point cloud, and are only shown as reference
{% endhint %}

#### Process

* On the Summary and Process page, click Process and Align
* The progress is shown on the bottom bar

{% hint style="info" %}
Known issues:

* The estimated processing times given are not accurate
* The Trajectory Solve process may take a few minutes, but the progress bar will remain at 0%. This is normal
  {% endhint %}

#### View

* Once the process is complete, you can view the scan in the View tab
* Multiple options exist to view and adjust color pallets, color mode, and more

{% hint style="success" %}
Protip: if your machine can handle it, you can increase the viewable points under the settings>display>point cloud display budget for a more detailed view of the scan&#x20;
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.freeflysystems.com/ecosystem/payloads/flux-lidar/beta-flux-desktop-app.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.