Learn what SimDirector in Prepar3D does and how to build, validate, test and share scenarios while avoiding broken triggers and object references.
SimDirector is Prepar3D’s built-in visual scenario editor. It lets you place aircraft and other objects, create routes, cameras, triggers, actions and instructional events, then preview the result inside the simulator. Open it from Prepar3D’s SimDirector command, build in edit mode, validate the logic, test from the start, and save a copy.
What can SimDirector create?
SimDirector creates interactive training exercises, demonstrations and mission-style scenarios without requiring you to write the entire scenario definition by hand.
- World objects: aircraft, vehicles and available scenery objects placed at specific positions and headings.
- AI movement: waypoint routes and supported behaviours assigned to non-player objects.
- Event logic: conditions and triggers connected to actions, messages, object activation or scenario outcomes.
- Training content: instructional prompts and Virtual Instructor behaviour where supported by the Prepar3D version in use.
- Presentation: camera objects and controlled viewpoints for demonstrations or briefings.
It is not an aircraft modeller, airport editor or gauge compiler. SimDirector arranges existing Prepar3D content and controls what happens during a scenario; separate development tools are needed to create the underlying models, effects or software modules.
How do you use SimDirector in Prepar3D?
The reliable workflow is to establish the starting flight first, add objects and logic in small stages, and test each stage before continuing.
- Load a simple base scenario. Select the user aircraft, starting position, time and weather in Prepar3D. Save it under a new name rather than modifying a supplied scenario.
- Open SimDirector. With the base scenario loaded, select the menu command labelled SimDirector. Its exact menu position and panel arrangement can differ between Prepar3D releases.
- Add an object. Select an aircraft, vehicle or scenery item from the panel commonly labelled Object Catalog, then place it in the 3D world. Use the properties panel to correct its position, heading, altitude and activation state.
- Define routes and relationships. Add waypoints where an AI object needs to move, then assign the route to that object. Check every object-reference field carefully; creating a route does not automatically tell an aircraft or vehicle to use it.
- Build the event chain. Start with one condition or trigger and connect it to one action. For example, entering an area might display an instruction, activate another object or update a goal. Confirm that this simple chain works before adding branches.
- Add cameras or instruction. Create presentation and training elements only after the underlying objects and triggers work. This makes faults much easier to isolate.
- Run validation. Use SimDirector’s validation function to find missing references and structurally incomplete objects. Validation cannot detect every logical mistake, such as a trigger radius placed in the wrong location.
- Preview from the beginning. Reset the scenario and run it as a user would. Test success, failure and reset paths, then save another versioned copy before making substantial changes.
A mistake we see constantly is testing only from the editor’s present state. An event may appear to work there but fail after a fresh load because an object was already active, a trigger had already fired or the test began beyond a waypoint.
Do you need the Prepar3D SDK for SimDirector?
You do not normally need a separate SDK installation to build scenarios from objects and behaviours already available in Prepar3D.
| Task | Use |
|---|---|
| Save an aircraft, location, weather and cockpit state | Prepar3D’s normal scenario-saving function |
| Place objects and create triggers, actions, routes or instructional events | SimDirector |
| Create models, compile gauges, develop software modules or package custom content | Prepar3D SDK and the relevant development tools |
Install the SDK that matches your Prepar3D release when the project uses custom assets or requires deeper development work. Our guide to installing and using the Prepar3D SDK explains the relevant components and why version matching matters.
SimDirector itself has changed between Prepar3D branches, including its object handling, cameras, waypoint actions, grouping and validation tools. The documented SimDirector changes introduced with Prepar3D v3.4 illustrate why a tutorial written for one release may not precisely match another. Do not assume a scenario using newer object types or actions will work in an older version.
Why do SimDirector objects or triggers fail?
Most SimDirector failures come from object state, broken references, incorrect placement or dependencies that are unavailable on the test system.
| Symptom | Likely cause and fix |
|---|---|
| An object is visible in the editor but missing during the scenario | Check its activation state, altitude and start conditions. Also confirm that the aircraft or scenery package supplying it is installed. |
| A trigger never fires | Verify that the trigger is active, references the intended object and uses a reachable condition or area. Temporarily enlarge proximity areas or simplify compound conditions while testing. |
| An AI object ignores its waypoints | Confirm that the waypoint list is assigned to that object, the object supports the requested behaviour and the route begins from a sensible position. |
| Validation passes but the scenario still stalls | The structure may be valid while the logic is impossible. Trace one trigger and action at a time, checking their initial states and activation order. |
| The scenario works only on its creator’s PC | It probably references an add-on, model, effect or other asset that is missing from the second installation. |
Can you share a SimDirector scenario?
Yes, but a SimDirector scenario should be treated as a set of instructions and references rather than a guarantee that every required asset is embedded.
Test it from the same folder structure and Prepar3D branch that recipients will use. List every required add-on, avoid redistributing third-party files without permission, and retain an untouched master copy. For the widest compatibility, build with default Prepar3D objects and avoid features introduced after the oldest simulator version you intend to support.