# Migrating Your Airplane from SeligSIM 2024.5 to SeligSIM 2026 **Purpose:** Move an airplane that YOU created in SeligSIM 2024.5 into a SeligSIM 2026 install, so it appears in the 2026 airplane selection list. **Scope:** Fixed-wing airplanes only. Applies to airplanes you built yourself; every airplane that shipped with 2024.5 and is still supported already ships with 2026. **Last updated:** 2026-09-20 --- ## 1. What this does, in one paragraph An airplane in SeligSIM is two folders with the SAME name: one holds the physics and configuration files, the other holds the 3D model and textures. You copy both folders from the 2024.5 install to the 2026 install, drop an empty "marker" file named after the airplane into the 2026 `AddNew` folder, and then click `Add New` in SeligSIM Power Tools 2026. Power Tools writes the airplane into the 2026 airplane list file immediately. The next time you start SeligSIM 2026, the airplane is in the list. --- ## 2. Before you start: assumptions and rules These instructions assume all of the following. 1. **Both versions are installed side by side** at their default locations: C:\SeligSIM 2024.5 C:\SeligSIM 2026 If yours are elsewhere, substitute your paths everywhere below. 2. **The airplane is one YOU created** in 2024.5 (your own folder name, your own files). 3. **The airplane's folder name does not already exist in 2026.** This is the one hard rule. Section 4 shows how to check. Never copy a folder over an existing 2026 folder of the same name. 4. **You are not migrating custom transmitter (Tx) settings.** The airplane will use the transmitter file named by the `PreferredController` line in its `Info.cfg`. That transmitter file ships with 2026, so nothing else needs to be copied for it. 5. **Copy, never move.** Leave the 2024.5 install exactly as it was. If anything goes wrong you can still fly the airplane in 2024.5, and you can repeat the copy. 6. **File compatibility is not a concern.** SeligSIM 2026 reads every 2024.5 airplane file format. No file needs editing or conversion. --- ## 3. Find the airplane's folder name Every airplane has ONE folder name that is used in two places. In the 2024.5 install: C:\SeligSIM 2024.5\Aircraft\FixedWing\\ physics, cfg files, Info.cfg C:\SeligSIM 2024.5\Graphics\Aircraft\FixedWing\\ 3D model (.ohm), textures Throughout this document `` stands for that name. Example: for an airplane you built in a folder called `MyCub60`, the two folders are C:\SeligSIM 2024.5\Aircraft\FixedWing\MyCub60\ C:\SeligSIM 2024.5\Graphics\Aircraft\FixedWing\MyCub60\ Confirm both exist, and confirm the first one contains a file named `Info.cfg`. Power Tools uses `Info.cfg` to recognize the airplane; without it the airplane will not show up in Section 7. **The two folders must keep the same name.** The physics folder's `ModelObj.cfg` points at the graphics folder by name (`Graphics\Aircraft\FixedWing\\...`). Do not rename either folder during the copy. --- ## 4. Check that the name is free in 2026 Look in both of these 2026 folders: C:\SeligSIM 2026\Aircraft\FixedWing\ C:\SeligSIM 2026\Graphics\Aircraft\FixedWing\ If a folder named `` already exists in EITHER place, **stop**. Do not copy over it. That folder belongs to an airplane that ships with 2026, and replacing it would break that airplane. Pick a different name for your airplane only if you are prepared to rename it consistently in 2024.5 first (both folders and the `mobjFileName` line in `ModelObj.cfg`); otherwise leave the airplane in 2024.5. --- ## 5. Copy the two folders Copy (do not move, do not cut) each folder to the matching place in 2026: | From (2024.5) | To (2026) | |---|---| | `C:\SeligSIM 2024.5\Aircraft\FixedWing\\` | `C:\SeligSIM 2026\Aircraft\FixedWing\\` | | `C:\SeligSIM 2024.5\Graphics\Aircraft\FixedWing\\` | `C:\SeligSIM 2026\Graphics\Aircraft\FixedWing\\` | **Using File Explorer:** open the 2024.5 folder, right-click ``, choose **Copy**; open the corresponding 2026 folder, right-click empty space, choose **Paste**. Do this once for the `Aircraft\FixedWing` pair and once for the `Graphics\Aircraft\FixedWing` pair. **Using a Command Prompt** (optional; same result): robocopy "C:\SeligSIM 2024.5\Aircraft\FixedWing\" "C:\SeligSIM 2026\Aircraft\FixedWing\" /E robocopy "C:\SeligSIM 2024.5\Graphics\Aircraft\FixedWing\" "C:\SeligSIM 2026\Graphics\Aircraft\FixedWing\" /E `/E` copies all subfolders, including empty ones. A robocopy exit code of 1 means "files copied" and is success, not an error. When done, the 2026 install has both folders, and 2024.5 is unchanged. --- ## 6. Create the marker file in the 2026 AddNew folder Power Tools looks for new airplanes in exactly one place: C:\SeligSIM 2026\Aircraft\FixedWing\AddNew\ For each airplane it wants to see there, it needs a file named .cfg The file's CONTENTS do not matter. It can be completely empty. Only the NAME matters, and it must match the airplane folder name exactly. For the `MyCub60` example the marker is C:\SeligSIM 2026\Aircraft\FixedWing\AddNew\MyCub60.cfg **Using File Explorer:** 1. Open `C:\SeligSIM 2026\Aircraft\FixedWing\AddNew\`. 2. Right-click empty space, choose **New > Text Document**. 3. Rename the new file to `.cfg`. Windows asks "If you change a file name extension, the file might become unusable. Are you sure?" Click **Yes**. **Watch out:** if File Explorer hides file extensions (the default on Windows), typing `MyCub60.cfg` produces a file actually named `MyCub60.cfg.txt`, and Power Tools will NOT see it. Turn on **View > File name extensions** in File Explorer first, then rename, and check that the name ends in `.cfg` and nothing else. **Using a Command Prompt** (optional; creates an empty file directly): type nul > "C:\SeligSIM 2026\Aircraft\FixedWing\AddNew\.cfg" **Do this BEFORE starting Power Tools.** Power Tools scans the `AddNew` folder once, when its Airplanes list is first opened in that run. A marker created while Power Tools is already open is not noticed until Power Tools is closed and started again. If you are migrating several airplanes, create one marker per airplane now, then do Section 7 once for each. --- ## 7. Add the airplane in Power Tools 2026 1. Make sure SeligSIM 2026 (the simulator itself) is NOT running. 2. Start **SeligSIM Power Tools** for the 2026 install (`SeligSIM_PT.exe` in `C:\SeligSIM 2026\`, or its Start menu shortcut). 3. Open the **Aircraft** section, then the **Airplanes** item under it. 4. In the **Category** drop-down, choose the category the airplane should be listed under in the simulator. **Recommended: `User Aircraft`.** Whatever category you pick, the airplane is ALSO added to `All Airplanes` automatically, so it is never lost. 5. In the list titled **New Airplanes [N]** (the N counts the markers found in `AddNew`), click your airplane. It is shown by the name from its `Info.cfg`, for example `My Cub 60 | by Me | Saito 91`, not by folder name. 6. Click **Add New**. That is all. Clicking `Add New` does three things at once: - writes the airplane into the 2026 list file `C:\SeligSIM 2026\Aircraft\FixedWing\Lists.cfg`, in the category you chose and in `All Airplanes` (placed right after the row that was selected in the current list); - deletes the marker file from `AddNew`; - removes the airplane from the `New Airplanes` list and shows it in the current category list. There is no separate Save button for this. The file is written the moment you click. You can close Power Tools right away. Repeat steps 4 to 6 for each additional airplane. --- ## 8. Verify in the simulator 1. Start SeligSIM 2026. 2. Go to the airplane selection screen. 3. Set the category drop-down to the category you chose (for example `User Aircraft`) and select your airplane. It also appears under `All Airplanes`. 4. Fly it. The transmitter is the one named by `PreferredController` in the airplane's `Info.cfg`, exactly as in 2024.5. --- ## 9. Troubleshooting | Symptom | Cause | Fix | |---|---|---| | `New Airplanes [0]` and `Add New` is grayed out | No marker found, or marker not seen | Confirm the marker is in `Aircraft\FixedWing\AddNew\` and ends in `.cfg` (not `.cfg.txt`). Close and restart Power Tools; markers are scanned once per run. | | Marker exists but the airplane is not listed | `Info.cfg` missing, or marker name does not match a folder | The marker `.cfg` must have a sibling folder `Aircraft\FixedWing\\Info.cfg`. Check spelling of both. | | Airplane loads in the sim with no 3D model, or an error about a missing `.ohm` file | The Graphics folder was not copied, or was copied under a different name | Copy `Graphics\Aircraft\FixedWing\\` with the SAME name as the physics folder. | | Airplane is in `All Airplanes` but not in the category I wanted | A different category was selected in the drop-down when `Add New` was clicked | Open the wanted category in Power Tools and use its list controls, or edit `Lists.cfg` by hand (Section 10). | | I added the wrong airplane | -- | In Power Tools, select it in the current list and click **Archive**. This removes it from the list and places a marker in `AddArchived\`, from which **Add Archived** can restore it later. The folders are not deleted. | --- ## 10. What changed on disk (for the curious) After a successful migration of `MyCub60` into `User Aircraft`: C:\SeligSIM 2026\Aircraft\FixedWing\MyCub60\ copied from 2024.5 C:\SeligSIM 2026\Graphics\Aircraft\FixedWing\MyCub60\ copied from 2024.5 C:\SeligSIM 2026\Aircraft\FixedWing\AddNew\MyCub60.cfg created, then deleted by Add New C:\SeligSIM 2026\Aircraft\FixedWing\Lists.cfg two lines added `Lists.cfg` is a plain text file. Each `[Category]` header is followed by one `[[FolderName]]` line per airplane; file order is the on-screen order. The two new lines look like this: [All Airplanes] ... [[MyCub60]] [User Aircraft] ... [[MyCub60]] Power Tools rewrites only the sections it changed and preserves the file's comments and section order. Editing the file by hand in a text editor is also fine: add or remove a `[[FolderName]]` line under the category you want. An airplane must be listed under `[All Airplanes]` to be complete; Power Tools takes care of that, a hand edit has to remember it. Nothing in the 2024.5 install is touched at any point. --- ## 11. AI skill summary Use this section when an AI assistant (for example Claude Code) is asked to migrate, copy, or "bring over" a user-created airplane from a SeligSIM 2024.5 install to a SeligSIM 2026 install, or to explain how a user can do it. Everything the assistant needs is in this file. **Inputs to obtain from the user:** - ``: the airplane's folder name under `Aircraft\FixedWing\` in 2024.5. - The two install roots, if not `C:\SeligSIM 2024.5` and `C:\SeligSIM 2026`. - The target category (default `User Aircraft`). **Preconditions to verify, in order, and stop on the first failure:** 1. `<2024.5>\Aircraft\FixedWing\\Info.cfg` exists. 2. `<2024.5>\Graphics\Aircraft\FixedWing\\` exists. 3. Neither `<2026>\Aircraft\FixedWing\\` nor `<2026>\Graphics\Aircraft\FixedWing\\` exists. 4. SeligSIM 2026 and Power Tools 2026 are not running. **Procedure:** 1. Copy (never move) the two folders to the same relative paths under `<2026>`. Keep the folder name unchanged. 2. Create an empty file `<2026>\Aircraft\FixedWing\AddNew\.cfg`. 3. Have the user start Power Tools 2026, open Aircraft > Airplanes, choose the category, select the airplane in `New Airplanes`, click `Add New`. The list file is written immediately; no save step. 4. Have the user start SeligSIM 2026 and confirm the airplane is listed under the chosen category and under `All Airplanes`. **Facts the procedure relies on:** - Power Tools scans `Aircraft\FixedWing\AddNew\*.cfg`; for each file it strips `.cfg` and requires the sibling `\Info.cfg`; markers without one are silently skipped. Only the marker's name is used; contents are ignored. The scan runs once per Power Tools run, when the Airplanes list is first opened. - `Add New` verifies `Info.cfg` again, deletes the marker, adds the airplane to the selected category and to `All Airplanes` when absent, and immediately rewrites `Aircraft\FixedWing\Lists.cfg` in place. There is no separate save step. - The airplane's transmitter is resolved by the sim from the `PreferredController` line in `Info.cfg`; every controller file a 2024.5 airplane can name ships with 2026, so no RadioEquip files are copied. - No airplane references shared resources outside its own two folders, so nothing else is copied. - 2026 reads all 2024.5 airplane files; no conversion. **Things NOT to do:** - Do not overwrite or merge into an existing 2026 folder of the same name. - Do not rename one folder without the other and `ModelObj.cfg`. - Do not copy `Lists.cfg` from 2024.5 over the 2026 one; it would drop every airplane new in 2026. - Do not copy `RadioEquip\Controllers\` files; Tx migration is out of scope. - Do not delete anything from the 2024.5 install.