Updated on 2017-12-11, viewed 378 times

Technical Reference - Database



Tacview database contains the definition of numerous civilian and military aircraft as well as many other objects you can find in a mission.

Every time Tacview loads a new object from some telemetry data, it will look for the corresponding best match in its database. The database entry can define the object default shape, color, as well as more advanced properties like engagement range, maximum speed, etc.

This database can be customized easily by creating XML files in the appropriate folder and filling then with definitions which will replace or complete the existing ones.

Future releases of Tacview will offer an integrated editor, so you will not have to mess with xml files anymore.

Extending and modifying Tacview database

Q11: I like to learn by example, can you share a demo file?

Here is example which shows how to declare an object based on an existing one and how to create custom SAMs with a specific engagement zone displayed as a sphere in Tacview.

Q12: Where can I find Tacview database?

Tacview default database is made of XML files embedded in Tacview executable. It is not possible to directly modify its content, however, you can easily extend and replace existing declarations by adding your own XML files as described in this documentation. The latest version of the database can be found on GitHub.

Q13: How can I extend or modify the existing database?

To extend or modify Tacview database, you need to create one or more XML files in the %ProgramData%\Tacview\Data\Database\Default Properties\ or %APPDATA%\Tacview\Data\Database\Default Properties\ folders.

You can create as many files as you want. Fell free to use subfolders to organise your data. Here is an example of an empty declaration file:

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<DefaultPropertiesCollection LoadingOrder="0.5">
	<!-- Put your definitions here -->

The LoadingOrder attribute is used to define in which order the XML files will be injected in the database. Files with the lowest numbers will be loaded first. Tacview uses numbers between 0.0 and 0.1 for its own definitions. You should use numbers between 0.5 and 1.0 for your own files, so your definitions will overwrite Tacview ones when applicable.

Defining objects default properties

Q21: Before going further, how can I know if I have made any mistake?

Any error detected by Tacview in the database files will be displayed in the debug console. You can display the debug console from Tacview help menu.