Introduction

This document is the starting point for creating IvAc FIR Definitions (aka FIRDEF). It describes the fundamental architecture behind the FIRDEF, including lots of samples provided by the original designers. This document also offers practical guidance to help you make better choices during your design and planning phase and guides you to the other documents in the SDK that contain more detailed information about how to address a specific task.

Translating that idea into actions requires some planning. Every FIRDEF relies heavily on design, and this design influences much of the XML code you need to write. So before you write any XML code, take the time to explore the possible techniques and technologies available for writing that code. Doing so can save you a lot of time and frustration.

It’s essential to keep the user experience uppermost in your mind as you design every aspect of your FIR Definition, from the way you define flight lists, to the colors used in your maps. Discover the guidelines that influence the look and behavior of your FIRDEF, in matters both general and specific.

Similar to the MTL (Multiplayer Traffic Library), the FIR Definitions are maintained on a central Terminal 2 server. On startup IVAC2 will query the central repository for new or updates to FIR Definitions and other data files used in IVAC2.

There are a lot of advantages:

• central management of IVAC2 data (single source)
• users will always have the latest version available
• local divisions are able to provide the latest and correct information
• ability to provide very detailed information to users
• global navigation data is provided by Logistics Dept.
• navigational data is separated from visual data
• no endless searches for an often outdated or incorrect sectorfile

The user will be able to select a FIR and ATC position to use from the FIR definition.

If you're new to IVAC 2 development start off by reading our First Steps guide.

Back