Flight simulation enthusiasts who invest time in customizing their Aerosimulations add‑ons for Prepar3D (P3D) know that those finely tuned configurations take hours—if not days—to perfect. System crashes, hardware upgrades, accidental deletions, or even a routine P3D update can wipe out that work in an instant. That’s why establishing a robust backup‑and‑restore strategy for your Aerosimulations settings isn’t just a good idea; it’s an essential part of professional simulator maintenance. This guide covers everything you need to know to safely preserve, version, and recover your Aerosimulations configuration files, whether you’re running a single home setup or managing multiple simulation stations.

Why a Dedicated Backup Strategy Matters for Aerosimulations Add‑ons

Unlike default P3D settings, which can often be regenerated, Aerosimulations add‑ons store unique calibration data, control mappings, panel states, and aircraft‑specific preferences. Losing these customizations forces you to manually re‑enter dozens of parameters, from throttle curves to avionics configurations. Moreover, Aerosimulations add‑ons frequently interact with other third‑party software (like FSUIPC, Active Sky, or PMDG’s systems), so your settings may also include carefully tuned offsets and integration points. A targeted backup ensures that your entire simulation ecosystem remains intact, saving you hours of re‑configuration and troubleshooting.

Identifying the Files You Need to Back Up

The first step in any backup plan is knowing exactly what to save. Aerosimulations configuration files are typically stored in the application data folder for Prepar3D. The default path is:

%APPDATA%\Lockheed Martin\Prepar3D v3\ (or v4 / v5 depending on your version)

Inside that folder, look for folders or files named Aerosimulations or abbreviated forms like ASim or AeroSim. Each add‑on may create its own subfolder. Common files include:

  • Configuration (.cfg) files – aircraft systems, lighting, weight, and fuel parameters.
  • Control assignment files – joystick, keyboard, and throttle quadrant mappings.
  • Panel state (.pst) files – saved cockpit states for different phases of flight.
  • Callibration files – for specific hardware, such as throttles or yokes.
  • Profile files – integration with external tools like SimConnect or FSUIPC.

Some Aerosimulations add‑ons also store settings in the P3D’s SimObject.cfg and aircraft.cfg files. To be safe, back up your entire Prepar3D application data folder alongside your add‑on folders. A reliable backup should also include the Documents\Prepar3D v5 Files folder if you store saved flights or scenarios there.

Manual Backup: Step‑by‑Step

For users who prefer direct control, manually copying the configuration files is straightforward. Follow these steps:

  1. Close P3D and all related tools (FSUIPC, external traffic, etc.) to prevent file locks.
  2. Navigate to %APPDATA%\Lockheed Martin\Prepar3D v5 (or your version).
  3. Locate every folder or file that belongs to Aerosimulations. If you’re unsure, search for “Aerosimulations” or “ASim” within the folder.
  4. Copy those items to a backup location, such as an external drive, a dedicated network share, or a cloud‑synchronized folder.
  5. Rename the backup folder with a date stamp (e.g., Aerosimulations_backup_2025-05-14) for easy identification.

Repeat this process after any significant change to your settings, such as new hardware mappings or an aircraft update.

Automating Backups with Scripts and Scheduled Tasks

Manual backups work, but they’re easy to forget. Automation removes that risk. Here are two efficient methods:

Using a Simple Batch Script

Create a .bat file that copies your Aerosimulations folders to a backup directory. For example:

@echo off
set source=%APPDATA%\Lockheed Martin\Prepar3D v5
set dest=D:\P3D_Backups\Aerosimulations_%date:~-4,4%%date:~-10,2%%date:~-7,2%
xcopy "%source%\aerosimulations*" "%dest%\" /E /I /Y
xcopy "%source%\ASim*" "%dest%\" /E /I /Y

Schedule this script using Windows Task Scheduler to run daily or weekly. The %date% variable creates unique folder names automatically.

Using PowerShell for More Granular Control

A PowerShell script can also include error logging and compress the backup. Example snippet:

$timestamp = Get-Date -Format "yyyyMMdd_HHmm"
$src = "$env:APPDATA\Lockheed Martin\Prepar3D v5"
$dest = "E:\Backups\AeroSim_$timestamp"
New-Item -ItemType Directory -Path $dest -Force
Copy-Item -Path "$src\*aerosim*" -Destination $dest -Recurse
Copy-Item -Path "$src\*ASim*" -Destination $dest -Recurse
Write-Host "Backup completed: $dest"

Both methods can be extended to copy additional folders like Documents\Prepar3D v5 Files.

Where to Store Your Backups: Balancing Safety and Accessibility

No storage medium is 100% failsafe. To protect against drive failures, fires, or ransomware, use a combination of local and remote storage.

  • External USB drives or NAS – fast, local recovery; but still vulnerable to the same physical risks as your main PC.
  • Cloud storage – services like OneDrive, Google Drive, or Dropbox provide off‑site protection. Be mindful of bandwidth limitations if you back up large P3D folders.
  • Versioned backups – use software that keeps multiple snapshots so you can roll back to a specific date. Tools like Veeam Agent or even Windows File History can help.

Many simmers combine a local automated script with a cloud sync tool (e.g., rclone or Resilio Sync) to keep an off‑site copy without manual intervention.

Restoring Aerosimulations Settings: A Detailed Walkthrough

When it’s time to restore—whether after a clean Windows install, a P3D upgrade, or a corrupted file—follow this sequence:

  1. Prepare the environment: Install P3D and all required Aerosimulations add‑ons exactly as they were when you made the backup. If you skip this step, the configuration files may reference components that don’t exist.
  2. Close P3D and all background processes (anti‑virus, FSUIPC, traffic add‑ons) to avoid file locks.
  3. Navigate to the backup location and open the folder corresponding to the date and state you want to restore.
  4. Copy the entire backup contents and paste them into the original application data folder (%APPDATA%\Lockheed Martin\Prepar3D v5), allowing file overwrites.
  5. Launch P3D and test the add‑ons. Load an Aerosimulations aircraft and verify that control bindings, displays, and system configurations are correct.
  6. If something is off, restart and try an older backup. Always keep at least three generations of backups.

For a more precise restore, you can copy only the Aerosimulations‑specific subfolders back, leaving other add‑ons untouched. This is useful if you only want to recover that particular aircraft’s settings.

Restoring Across Different Systems or P3D Versions

Moving your Aerosimulations configurations to another PC—or upgrading P3D from v4 to v5—requires extra care. The configuration files may contain hard‑coded paths or version‑specific entries. Follow these best practices:

  • Install the exact same Aerosimulations product versions on the target system. A newer aircraft update may change the format of the configuration files, breaking your backup.
  • Use a fresh backup taken from the old system immediately before the transition.
  • Manually compare control assignments after restore—axis calibration settings often need recalibration if you use different hardware or drivers.
  • Test each add‑on individually before flying a full mission. Start with a simple cold‑and‑dark state, then proceed to full systems check.

If you’re upgrading P3D major versions, note that the application data folder name changes (e.g., from Prepar3D v4 to Prepar3D v5). After installing v5, navigate to the new folder and copy the Aerosimulations backup there. Some users have reported success with direct copy, but others need to reapply configurations through the add‑on’s UI. Always consult the product’s documentation first.

Troubleshooting Common Restore Problems

Even with a careful process, things can go wrong. Below are frequent issues and their solutions.

Conflicting Settings After Restore

If your restored settings cause P3D to crash or behave erratically, the backup may have been taken while the simulator was running, leading to partially saved files. Always restore from a backup created when P3D was fully closed.

Files Not Found or Missing Entries

After restoring, you might see “configuration file missing” errors. This often means the backup didn’t include all the necessary folders. Re‑examine the original source and copy the full directory tree, including hidden subfolders.

Hardware Calibration Drift

Joystick throttle mappings may feel different after restore. This is usually due to different axis ranges or Windows USB port changes. Use the Aerosimulations control setup page to recalibrate, then make a fresh backup.

Corrupted Backup Files

If the backup folder is damaged (e.g., from a sync error), try restoring from an older generation. That’s why maintaining multiple versions is critical. Cloud sync tools can sometimes corrupt files if the sync is interrupted—verify backup integrity by periodically opening the files with a text editor.

Additional Best Practices for Long‑Term Maintenance

  • Version‑control your backups with meaningful names: Backup_2025May14_BeforeFSUIPCUpdate. This helps you track what changed.
  • Test your restore process quarterly. If you can’t restore from a backup, that backup is worthless.
  • Keep a recovery document listing every add‑on, its version, and the backup location. Include installation notes and serial numbers.
  • Use robust cloud storage with end‑to‑end encryption for off‑site copies. For large folders, consider using rclone encrypted remotes.
  • Don’t rely solely on Windows System Restore – it may not capture the application data folder correctly.

Conclusion

Backing up your Aerosimulations settings is a small investment that pays dividends every time you upgrade a system, replace a drive, or recover from an unexpected crash. By identifying the right files, automating the process, storing copies in multiple locations, and regularly testing your restoration workflow, you ensure that your carefully crafted simulation experience can survive any incident. The time you spend setting up a proper backup routine will be nothing compared to the hours saved when disaster strikes.