Simulator Configuration
The Simulator Configuration panel allows operators to define which crew positions are available in the simulator editing form. This replaces the previously fixed position list with a fully configurable selection, so the form can be tailored to the operator's actual operations.
Where to find it
Go to Settings → section Crew → Simulator Configuration.
The panel layout is similar to the Flight Editing settings view.
Configuring available positions
Inside the Simulator Configuration panel, there is a Positions option. Clicking it opens a pop-up with a multiselect field where you can choose which positions to show in the simulator form.
You can select any positions from both the Cockpit and Cabin categories.
At least one position must be selected — the form will not save an empty list.
By default, the positions previously displayed in the simulator window are preselected.
The multiselect field works like a tag/rating picker — start typing to filter available positions, then click to add them to the selection.
How does it affect the simulator form
Once saved, the configured position list is reflected everywhere the simulator editing form appears:
Crew Calendar — when creating or editing a simulator entry
Crew Timeline — when creating or editing a simulator entry
OPS tab — the same position list applies
If a simulator entry already has a crew member assigned to a position that is not in the configured list, that position is still displayed in the form to preserve the existing assignment — it simply won't appear as an option for new assignments.
Default behaviour (no configuration set)
If the position list has never been configured (empty configuration), Leon falls back to the built-in default set of simulator positions — the same positions that were available before this feature was introduced.
Auto-assignment logic
When a simulator is added directly from the Crew Panel for a specific crew member, that crew member is automatically assigned to the first position in the configured list (sorted by order). This behaviour is the same as before — the configuration change does not affect it.