The new built-in simulator in EuroScope

Conceptual changes

There are two main conceptual changes in the simulator environment:

· I simply deleted the buil-in FSD server. There is no way anymore to connect to a running ES session with another ES client. All simulations are running against an FSD server. It most cases it can be SweatBox. I also provide an FSD server for those who has no right to use SweatBox, who would like to run a private session or who would like to use the extended services like 3D tower simulation - see later.

· The old concept of connecting several ES sessions to a server and run distributes simulations are not deleted completely, but treated as obsolete. In the way there is only one ES that simulates all planes. The pseudo pilots are also connected to the server, allocates planes to be flown by them like tracking them on the radar. After allocating a plane the pseudo pilots sends only the instructions to the simulator and the planes are simulated remotely. That way all problems with transfer of simulations have gone.

EuroScope FSD server

As far you are using VATSIM's SweatBox server you have comply the rules of VATSIM. If you would like to use the simulator without it you may use the packed lightweight FSD server. It is lightweight as there is no user control, no password checking or anything like that. On the other hand it has extra features like the connection to FSD for 3D tower view.

It is very important for us that the FSD server of EuroScope is planned to be used in a commercial product as well. It is freely available for the VATSIM community but with some restrictions:

· The maximum number of controllers to be connected is limited to 2. If you need more you may use the SweatBox server.

· The maximum number of FSX connections are limited to 2 to avoid 180 degrees or more detailed 3D views, but fun for home.

· To run the FSD server you must be connected to the internet and the server is looking for license file at euroscope.hu website. The license file is time limited and will be extended by me time to time. Still we have the right to terminate the license file download at any time without prior notifications.

To run the EuroScope FSD server just doubleclick on the EXE. It will prompt for the license file. Select the "PublicVatsimLicence.lic" file. Using this file the server will be able to download the real license and run the server. For further information check the "System messages" area of the server.

Using the FSD server you can specify a scenario file at the server side. Then all connected clients will receive the appropriate part of the scenario. This way it is not necessary to load the same file to all controllers. Because of this feature it is now possible to start an ES session as SweatBox session without specifying a scenario file.

ESE file changes

There is a new section in the scenario file, the ground network description:

[GROUND]

In this section you can define the taxi network. The complete network should be built up from the smallest pieces of the taxiways. One piece can be defined in the following way:

TAXI:<taxiway name>:<maximum taxi speed>[:<network bitwise flag>[:<end point name>]]
COORD:46.9328792422935:28.9203830272504

COORD:46.9343205884423:28.9204478900479

COORD:46.9344374416802:28.9204193684806

COORD:46.934554294663:28.9203433109678

COORD:46.9346679014852:28.9202197175094

The "taxiway name" is mostly to the reader. It is used only in the direct TAXI menu. There the code ignores the letters after '/' char and ignores the taxiways that has '-' in the name. The base idea is to use the taxi way name where it is really the taxiway. Use 'A1-A2' where you define a junction between ways. And use 'A1/A1-G78' where there is an internal junction along a taxiway.

The "maximum taxi speed" defines the speed limit for the simulator when using that taxiway.

The "network bitwise flag" can be used to define discrete taxi networks. One for the planes another for follow me cars, or any other vehicles. But a taxiway can be used by different networks. Here the bits of the number defines what vehicles can be used. We suggest using 1 for the planes.

The "end point name" defines a final segment of the network. It is a gate a stand or a holding point where you normally end taxiing.

Scenario file changes

PSEUDOPILOT

You may split a scenario into pieces using the PSEUDOPILOT keyword. The section that follows this key will be used only by the pseudopilot with the given callsign:

PSEUDOPILOT:<callsign>

The callsign may be 'ALL' to define a section for all pseudopilots.

ILS

The ILS works as before, but for a greater precision you may define the heading using double value or define the far end point instead of heading:

ILS13R:47.4483272:19.2214439:130.0
ILS26:46.9282694:28.9544833:46.9273167:28.9073639

ROUTE

You can define routes that the planes may fly. The selected route will be added to the route section and the plane will start flying to the end point of the closest segment. The route is built up from named points separated by space. To define the requested altitude enter a /<altitude> just after the name. The final piece of the route may be ILS definition too. The rotes may be used to define traffic patterns, missed approaches, visual approaches, etc.

ROUTE:ANEDO4A:ANEDO NATIV VESIK IF08 FAP08/2500

ROUTE:ANEDO4A:ANEDO NATIV VESIK IF08 FAP08/2500 ILS08

To select a route you can click with the RIGHT button to the ROUTE in the toolbar. Then just select on from the list.

METAR

With this keyword you may define meteorological situations that should be sent to FSX.

METAR:LUKK 292000Z 32004KT CAVOK 11/06 Q1012 NOSIG

Use the ".metar" keyword to open the dialog.

SIMDATA

Use this key to override some default value for the 3D view or for the simulator itself. Use '*' where the default value to be used.

SIMDATA:<clalsign>:<plane type for FSX>:<livery for FSX>:<max taxi speed>:<taxiways>:<extent>

The "callsign" is to identify the plane.

Normally the type from the flight plan and the first three letters from the callsign is sent to FSX for type and livery matching. You may change it with "plane type for FSX" and "livery for FSX".

The "max taxi speed" defines the highest speed of the vehicle.

The "taxiways" is a bitwise value again. It defined which taxiways the vehicle can use. ES calculates a bitwise AND between this value and the taxiway similar value. If it is not 0 then the vehicle can use the taxiway.

The "extent" is a simple value used to detect if two objects are too close to each other on the ground.

INITIALPSEUDOPILOT

This keyword defines which pseudo pilot will be the default driver of the plane. In the new structure no one can instruct a simulated plane without assuming as driver. To speed up this process the default callsign can be defined.

INITIALPSEUDOPILOT:LUKK_P_APP

When this controller logs in the plane simulation is allocated for him.

In the package in LUKK folder you can find a complete example about ESE changes and new scenario file. You may start working with this session.

The scenario file editor

Start it from the menu. The following dialog appears:

First it is empty. Click the "Load" button to 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 or even a playback. 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 follow the session with the new data.

I hope the usage of the dialog is straightforward.

The FSX connector

There is a third executable in the package, the FSX connector. It can be connected to the EuroScope FSD server and a running FSX session. It transfers the simulation data from the ES session to FSX and shows the planes as precisely as possible. When an FSX connector is connected to the server the simulator ES sends the plane updates in every 1 second instead of every 5-6 seconds to make the tower view as smooth as possible.

Be sure to define for the connector the path where the plane definitions are stored. It will use for special effects like fire, smoke and lights. So far just ignore the "Type/Livery override" and the METAR stuff. The "ground clamp" works with Prepair3D but not with FSX. Therefore some objects may be below the ground. But I will fix it later.

To ensure that FSX uses the same planes as the connector be sure the you have defined the same folder in the fsx.cfg file (normally at c:\Users\<usernam>\AppData\Roaming\Microsoft\FSX\fsx.CFG). Here check:

SimObjectPaths.6=SimObjects\UT2 Aircraft

or similar, depending the livery pack you have.

In the package you find a folder "CenterFire". This folder contains effects the tower view uses for lights, smokes, engine fire and even for collision. Be sure to have them in a place where available for FSX.

New TAG items

There are new TAG items that can be used for simulator. Mostly for pseudo pilots. They are active only in case the connection type is "SweatBox", so you bay define them on regular family as well.

The indicators are the followings:

· Simulation indicator - It indicates who is the driver of the plane:

o {} - no driver so far

o {*} - you are the driver - also with yellow when it is just transferred to you

o {APP} - the ID of driver controller

· Simulation waypoint - The next waypoint of the route

Also there are new functions:

· Simulation popup - to popup the assume/transfer of simulation

· Simulator holding points - to easily start holdings

· Simulator land and vacate - to pop up the RWY selection, the low approach, touch and go and also the vacate direction menu

· Simulator next waypoints - to set a shortcut

· Simulator takeoff popup - Line up, takeoff, abort takeoff menus

· Simulator taxi behind be - To select the plane to taxi behind

· Simulator taxi popup - To other taxi options popup