Scenario editor

From EuroScopeWiki

Revision as of 17:19, 11 May 2014; view current revision
←Older revision | Newer revision→
Jump to: navigation, search
Previous: Running a simulator session Actual: Scenario editor Next: Tower simulator

Contents

The dialog

Image:ScenarioEditorDialog32.gif

After opening the dialog box is just completely empty. You should load the scenario data first, or start editing a new one from scratch. To load some existing data click the "Load" button. A popup menu appears where you can define what you would like to edit. You have the following options:

  • Load from file - Just load a scenario, edit and save. This is the most common way of the editor.
  • Load current situation - With this option the current radar client situation is loaded. It may be a live VATSIM connection or a simulation session, a playback or even a live situation when connected to an SBS. All planes, flight plans are loaded. You may filter, change and save for a further scenario.
  • Load current simulation - Similar to the prior one, but it loads the data from the simulator.
  • Attach editor to the simulator - using this you may edit the currently running simulation. While you are editing the simulator is paused. You may add, delete planes. Then save the situation or continue the session with the new data.

After loading the data you may see the file name at the top edit box. Use the other buttons:

  • Save - Save the edited scenario to the file it was loaded or saved before.
  • Save as - Save the edited scenario to a new file.
  • Close - Close and discard all the changes.


The dialog is built up from sections where you can edit different areas of the scenario file.


ILS data

The number of runways you may define for a scenario is still limited to 4. They can be edited in the ILS section:

  • ILS combo - Select the RWY you are to be edited.
  • Treshold - The position of the treshold.
  • Name - The name of the RWY.
  • Far end - From 3.2 you may define the RWY not only by its direction but by to points. Fill the far end coordinates here.
  • Heading - The old method is still available, hence the precision of the heading is increased.
  • Import - Use this button, select an existing scenario file and import the ILS section from it.
  • From screen - Using this button you may define the RWY by clicking the treshold and the far end on the screen.


Airport altitude

This general information is not in any group.


Performance data

This section is not yet utilized.


Holdings

Here you can add, delete or modify the holdings data:

  • List - Select any of the holdings to be modified.
  • Point - The main point of the holding.
  • Heading - The inbound course.
  • Turn - The turning direction.
  • Import - See above.
  • Add - To add a new holding pattern.
  • Delete - To delete the selected one.


Controllers

Here you can add, delete or modify the simulated controllers:

  • List - Select any of the controllers to be modified.
  • Callsign - The desired callsign of the simulated controller.
  • Frequency - The primary frequency of the controller.
  • Simulator - Obsolete. See the Scenario file description in the Simulator Architecture.
  • Import - See above.
  • Add - See above.
  • Delete - See above.


Predefined routes

Here you can add, delete or modify predefined routes for the session:

  • List - Select any of the routes to be modified.
  • Name - The name of the predefined route.
  • Text box - In the text box you can define the route point by point. After each point you may define altitude with a /.
  • Import - See above.
  • Add - See above.
  • Delete - See above.


METARS

Here you can add, delete or modify quick METAR descriptions:

  • Text box - Here you do not have Add and Delete buttons. Edit the METAR lines in the text box in a way that each line should form a complete, well defined METAR. The station name is not important as the weather is set globally to FSX/P3D.
  • Import - See above.


Planes

This part has the most amount of controls. But basically it works the same way as the prior ones:

  • List - Select any of the planes to be modified.
  • Callsign - The callsign of the plane.
  • Reconnect - If you change the callsign of a plane while editing a live simulation session data, press this button to force a reconnect of this plane to the server.
  • IAS variation - The average variance of the speed from the performance defined value.
  • Delay - Obsolete. Since the new architecture the simulated planes are reacting immediately.
  • Position - The initial position of the plane. You may enter the coordinate here manually. Or drop down the combo box. It is filled with the positions defined for the TAXI network in the ESE file (ESE Files Description). Or press the From screen button to position the plane by mouse clicks.
  • On the ground - Set this check box to indicate if the simulation starts on the ground. The altitude is set to the airport level automatically.
  • From screen - After clicking on this button you may define the plane position by mouse. The first click defines the position and the second one defines the heading.
  • Start at - How many minutes after the session is started should the plane appear on the screen.
  • Heading - The initial heading of the plane. It is used on the ground only. Otherwise it is calculated from the route and position.
  • Altitude - The initial altitude/level of the plane.
  • Requested altitude - The initial climb or descend altitude/level.
  • at - At which point the plane should be at Requested altitude.
  • Squawk - The code set by the plane.
  • Flightplan - Short extract of the flight plan data. It is readonly here.
  • Edit - Press this button to edit the flight plan in the Flight Plan Setting Dialog.
  • Route - The point by point route the plane should follow. From v3.2 it may be empty. That case the route extracted from the flight plan will be used.
  • From FP - Press this button to extract the route data from flight plan just now.
  • Simulator - Obsolete. See the Scenario file description in the Simulator Architecture.
  • Initial pilot - Who will be the initial pseudo pilot of the plane. If empty, someone have to get the simulation manually before issuing any command.
  • Sym type - The type data to be sent to FSX connector (see Tower simulator). If empty then the plane type from the flight plane will be used.
  • Livery - The livery data to be sent to the FSX connector (see Tower simulator). If empty, then the first three letters of the callsign is used.
  • Taxi speed - The maximal taxi speed of the pane/object.
  • Taxiways - The code value that defines which taxiways the plane/object can use. See the taxiway definitions in ESE Files Description.
  • Extent - the size of the aircraft/object. It is used for collision detection.
  • Add - See above.
  • Delete - See above.



Previous: Running a simulator session Actual: Scenario editor Next: Tower simulator
Personal tools
Tower view
FAQ