# ACMI Telemetry File Format Tacview's universal public file format makes it is possible to easily export flight data from the simplest programming language. Written in plain UTF-8 text, the syntax is easy to read yet offers a very powerful way to set and change – in real-time – any property of any object on the battlefield. For instance, it is possible to change the coalition, the color, even the type of an object, on the fly. In the same way, you can easily assign and change global properties. ### Introduction to the format v2.2 Without further ado, let's start with the simplest file possible: ``` FileType=text/acmi/tacview FileVersion=2.2 ``` These are the only two mandatory lines you must put first in any ACMI file. This header tells Tacview which format to expect. Any following data is optional. Let's add some more information: ``` FileType=text/acmi/tacview FileVersion=2.2 0,ReferenceTime=2011-06-02T05:00:00Z #47.13 3000102,T=41.6251307|41.5910417|2000.14,Name=C172 ``` To better understand this structure, we need to know that – apart from its header – each line of the file can be either: * The sharp sign # introducing a new time frame in seconds relative to ReferenceTime * An object id (in this example 0 and 3000102) followed by as many properties as you want separated by commas ,. Each property will be assigned a new value using the equal sign =. * The third possibility – not shown here – is a line which starts with the minus sign - followed by the id of an object we want to remove from the battlefield (could be destroyed or simply out of recording range). Let's see in detail each line syntax: ``` 0,ReferenceTime=2011-06-02T05:00:00Z ``` This line assigns the value `2011-06-02T05:00:00Z` to the property `ReferenceTime` of the global object always designated by its id zero `0`. In other words: This line defines the base/reference time used for the whole flight recording. To understand better what this means, let's have a look at the following line: `#47.13` This line defines a time-frame in seconds relative to `ReferenceTime`. In that case, this means that the following events or properties happened at `ReferenceTime + 47.13 seconds` ⇒ `2011-06-02T05:00:00Z + 47.13` ⇒ `2011-06-02T05:00:47.13Z` Now let's see the following line: ``` 3000102,T=41.6251307|41.5910417|2000.14,Name=C172 ``` This line defines two properties for the object `3000102`. To save space, Object ids are expressed in [hexadecimal](https://en.wikipedia.org/wiki/Hexadecimal) without any prefix or leading zeros. The first property `T` (which stands for Transform) is a special property used to define the object coordinates in space. We will see later which syntaxes are supported for `T`. For now, let's just focus on this case which is: `T = Longitude | Latitude | Altitude`. Notice that `Latitude` and `Longitude` are expressed in degrees. Positive values are toward the north and east directions. Since the whole file is always in the metric system, the altitude is expressed in meters [MSL](https://en.wikipedia.org/wiki/Metres_above_sea_level) (above sea level, also known as ASL in some countries). The following property `Name` obviously defines the object name `C172` which is a short way of designating a [Cessna 172](https://en.wikipedia.org/wiki/Cessna_172) aircraft. Now that you know all the basics to create a flight recording, let's move our new aircraft a bit further to the east. To do so, we can simply add another frame to our file: ``` #49 3000102,T=41.626|| ``` As you can see, we have defined a new longitude value `41.626` for our aircraft at the time frame `2011-06-02T05:00:49Z`. You may have noticed that we don't need to specify – again – the aircraft name, simply because it has not changed since the last time! Another difference with the previous record is that we have omitted the latitude and altitude parameters because they did not change either. This helps to save a lot of space when generating data for long flights. While aircraft are usually quite mobile, this optimization is especially relevant for ground objects which can stay still or move just a little bit time to time... ### Detailed File Specifications Now that you are starting to understand better how ACMI files are structured, let's review together the requirements and some tips related to the file format in general: **Requirements** * Text data must be written in UTF-8. That way, all languages are supported for text properties. * All data are expressed in the metric system, using meters, meters per second for speed, degrees for angles, [UTC time](https://en.wikipedia.org/wiki/Coordinated_Universal_Time) and so on. * Object ids are expressed using 64-bit hexadecimal numbers (without prefix or leading zeros to save space) * The object `0` is used to define global properties (like `ReferenceTime` or `Briefing`) * When you want to assign a text property which contains a comma , you must put the escape character `\` before it so it is not interpreted by Tacview as the end of your string. ``` Briefing=Here is a text value\, which contains an escaped comma in it! ``` **Tips** * To save space, it is strongly suggested to end lines with the LF `\n` character only. * It is cleaner to prefix text data with the UTF-8 [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) header. * The whole of the text data can be wrapped in a zip or 7z container to save bandwidth or disk space. * Data can be presented out-of-order. Tacview will do its best to reorder it in memory. ### Object Coordinates Now let's have a closer look at the different notations for object coordinates. To optimize the file size, Tacview offers four different notations. Here are two examples: When exporting a bullet coordinate, we do not need any data about its rotation angles. The opposite example would be an aircraft in a flight simulator running in a flat world like Falcon 4.0: In that case, to get accurate replay, we should export the native position of the aircraft in the flat world, its rotation, and its coordinates in a spherical world. That way the aircraft will not only be properly displayed in Tacview's spherical world, but telemetry calculation will be done in the object's native coordinate system so the numbers visible on screen will match the ones you can see in the original flight simulator. **Object Position Syntax #1** `T = Longitude | Latitude | Altitude` Simple objects in a spherical world (typically minor objects like bullets). Can also be relevant for low-end data source like GPX files without rotation information. **Object Position Syntax #2** `T = Longitude | Latitude | Altitude | U | V` Simple objects from a flat world. U & V represent the native x and y. Do not forget to express them in meters even if the original coordinates are in feet for example. Altitude is not repeated because it is the same for both native and spherical worlds. **Object Position Syntax #3** `T = Longitude | Latitude | Altitude | Roll | Pitch | Yaw` Complex objects in a spherical world. Roll is positive when rolling the aircraft to the right. Pitch is positive when taking off. Yaw is clockwise relative to true north. **Object Position Syntax #4** `T = Longitude | Latitude | Altitude | Roll | Pitch | Yaw | U | V | Heading` Complex object from a flat world. Same as before. Heading is the yaw relative to the true north of the flat world. It is required because the native world north usually does not match spherical world north because of projection errors. | Remember that you can omit the components which did not change since the last time. This will save a lot of space. If some of the data is missing (for example object rotation), Tacview will do its best to emulate it in order to give a nice replay. Independently from optimization, you should keep the same data notation for each object during the object life. If at one point you use a different notation, Tacview will do its best to promote the object to a more complex one. However – because of the initial lack of data – the final result may not be the expected one. ### Global Properties We already saw that one of the most important global properties is the `ReferenceTime`. Obviously, there are plenty of other meta-data you can inject in a flight recording to make your replay more detailed. **Text Properties** | Property Name | Meaning | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `DataSource` |

Source simulator, control station or file format.
DataSource=DCS 2.0.0.48763
DataSource=GPX File

| | `DataRecorder` |

Software or hardware used to record the data.
DataRecorder=Tacview 1.5
DataRecorder=Falcon 4.0

| | `ReferenceTime` |

Base time (UTC) for the current mission. This time is combined with each frame offset (in seconds) to get the final absolute UTC time for each data sample.
ReferenceTime=2011-06-02T05:00:00Z

| | `RecordingTime` |

Recording (file) creation (UTC) time.
RecordingTime=2016-02-18T16:44:12Z

| | `Author` |

Author or operator who has created this recording.
Author=Lt. Cmdr. Rick 'Jester' Heatherly

| | `Title` |

Mission/flight title or designation.
Title=Counter Attack

| | `Category` |

Category of the flight/mission.
Category=Close air support

| | `Briefing` |

Free text containing the briefing of the flight/mission.
Briefing=Destroy all SCUD launchers

| | `Debriefing` |

Free text containing the debriefing.
Debriefing=Managed to stay ahead of the airplane.

| | `Comments` |

Free comments about the flight. Do not forget to escape any end-of-line character you want to inject into the comments.
Comments=Part of the recording is missing because of technical difficulties.

| | `MapId` |

A unique text identifier that designates the location where the mission takes place. This can be useful to automatically enable or disable terrain layers during debriefing.
MapId=NuclearOption.Heartland

| **Numeric Properties** | Property Name | Unit | Meaning | | ------------------------------------------------------------------------ | ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |

ReferenceLongitude
ReferenceLatitude

| deg |

These properties are used to reduce the file size by centering coordinates around a median point. They will be added to each object Longitude and Latitude to get the final coordinates.
ReferenceLongitude=-129
ReferenceLatitude=43

| **Events** Events can be used to inject any kind of text, bookmark and debug information into the flight recording. They are a bit special: They are declared like properties, but unlike properties, you can declare several events in the same frame without overriding the previous one. Here is an example on how to inject events: ``` #8.62 0,Event=Message|3000100|Here is a generic event linked to the object 3000100 0,Event=Bookmark|Here is a bookmark to highlight a specific part of the mission! #8.72 0,Event=Debug|Here is some debug text, visible only with the /Debug:on command line option ``` You may notice the structure of an event declaration: ``` Event = EventType | FirstObjectId | SecondObjectId | ... | EventText ``` For each event we must declare first the type of the event (e.g. `Bookmark`), optionally followed by ids of concerned objects. For example, when the user double click on the event, Tacview will use theses ids to automatically center the camera around associated objects. The last part is a mandatory text message. Even if it is possible to provide an empty text, it is suggested to provide a useful message to get the most out of your debriefings. Here are the different kind of events currently supported by Tacview: | Event Name | Meaning | | | | | | | | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | ------------------------------------------------------------- | ----------- | ---------------------- | ------------ | --------------------- | ----------------------- | | `Message` |

Generic event.
0,Event=Message | 705 | Maverick has violated ATC directives

| | | | | | | `Bookmark` |

Bookmarks are highlighted in the time line and in the event log. They are easy to spot and handy to highlight parts of the flight, like a bombing run, or when the trainee was in her final approach for landing.
0,Event=Bookmark | Starting precautionary landing practice

| | | | | | | | `Debug` |

Debug events are highlighted and easy to spot in the timeline and event log. Because they must be used for development purposes, they are displayed only when launching Tacview with the command line argument /Debug:on
0,Event=Debug | 327 active planes

| | | | | | | | `LeftArea` |

This event is useful to specify when an aircraft (or any object) is cleanly removed from the battlefield (not destroyed). This prevents Tacview from generating a Destroyed event by error.
0,Event=LeftArea | 507 |

| | | | | | | `Destroyed` |

When an object has been officially destroyed.
0,Event=Destroyed | 6A56 |

| | | | | | | `TakenOff` |

Because Tacview may not always properly auto-detect take-off events, it can be useful to manually inject this event in the flight recording.
0,Event=TakenOff | 2723 | Col. Sinclair has taken off from Camarillo Airport

| | | | | | | `Landed` |

Because Tacview may not always properly auto-detect landing events, it can be useful to manually inject this event in the flight recording.
0,Event=Landed | 705 | Maverick has landed on the USS Ranger

| | | | | | | `Timeout` |

Mainly used for real-life training debriefing to specify when a weapon (typically a missile) reaches or misses its target. Tacview will report in the shot log as well as in the 3D view the result of the shot. Most parameters are optional. SourceId designates the object which has fired the weapon, while TargetId designates the target. Even if the displayed result may be in nautical miles, bullseye coordinates must be specified in meters. The target must be explicitly (manually) destroyed or disabled using the appropriate properties independently from this event.
0,Event=Timeout | SourceId:507 | AmmoType:FOX2 | AmmoCount:1 | Bullseye:50/15000/2500 | TargetId:201 | IntendedTarget:Leader | Outcome:Kill

| ### Object Properties Object properties may be set and changed in real-time. Even if new properties may not always be visible in the 3D view, you can always have a look at the raw telemetry window to see what is the current value of each property for currently selected objects. Tacview's [database](https://raia-software-inc.gitbook.io/tacview/customization/database) enables you to predefine any of the object properties except for Type and Name. For example, you can predefine the default shape of a F-16C in that database. If the `Shape` property value is not defined in the telemetry file, Tacview will use the value stored in the database and display your custom 3D model for the F-16C in the 3D view. **Text Properties** | Property Name | Meaning | | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Name` |

The object name should use the most common notation for each object. It is strongly recommended to use ICAO or NATO names like: C172 or F/A-18C. This will help Tacview to associate each object with the corresponding entry in its database. Type and Name are the only properties which CANNOT be predefined in the Tacview database.
Name=F-16C-52

| | `Type` |

Object types are built using tags. This makes object management much more powerful and transparent than with the previous exclusive types. (see below for the list of supported types). Type and Name are the only properties which CANNOT be predefined in Tacview database.
Type=Air+FixedWing

| | `AdditionalType` |

Any tags defined here will be added to the current object Type. This is useful to force an object type which has not been defined explicitly in the telemetry data. For example, you can use this property to automatically set the FixedWing tag for a Cessna 172 telemetry data which come from a Garmin csv file (which usually does not contain any type declaration). For obvious reasons, this property must be used only in Tacview database, NOT in telemetry files.
\Air+FixedWing\

| | `Parent` |

Parent hexadecimal object id. Useful to associate for example a missile (child object) and its launcher aircraft (parent object).
Parent=2D50A7

| | `Next` |

Hexadecimal id of the following object. Typically used to link waypoints together.
Next=40F1

| | `ShortName` |

This abbreviated name will be displayed in the 3D view and in any other cases with small space to display the object name. Typically defined in Tacview database. Should not be defined in telemetry data.
ShortName=A-10C

| | `LongName` |

More detailed object name, used in small windows where there is more space than in a cluttered 3D view, but not enough space to display the full detailed name. For readability, it is suggested to start by the short name first (usually an abbreviation like the NATO code), followed by the object nickname / NATO name. Typically defined in Tacview database. Should not be defined in telemetry data.
LongName=A-10C Thunderbolt II

| | `FullName` |

The full object name which is typically displayed in windows and other logs wherever there is enough space to display a lot of data without clutter issues. Typically defined in Tacview database. Should not be defined in telemetry data.
FullName=Fairchild Republic A-10C Thunderbolt II

| | `CallSign` |

The call sign will be displayed in priority over the object name and sometimes pilot name, especially in the 3D view and selection boxes. This is handy for mission debriefings where call signs are more informative than aircraft names.
CallSign=Jester

| | `Registration` |

Aircraft registration (aka tail number)
Registration=N594EX

| | `Squawk` |

Current transponder code. Any code is possible, there is no limitation like with the old 4 digit transponders.
Squawk=1200

| | `ICAO24` |

Mode S equipped aircraft uniquely assigned ICAO 24-bit address.
ICAO24=A72EC8

| | `Pilot` |

Aircraft pilot in command name.
Pilot=Iceman

| | `Group` |

Group the object belongs to. Used to group objects together. For example, a formation of F-16 flying a CAP together.
Group=Springfield

| | `Country` |

ISO 3166-1 alpha-2 country code.
Country=us

| | `Coalition` |

Coalition
Coalition=Allies

| | `Color` |

Can be one of the following: Red, Orange, Yellow (Tacview 1.8.8), Green, Cyan (Tacview 1.8.8), Blue, Violet. Colors are predefined to ensure a clear display of the whole battlefield in all conditions. Colors may also be customized.
Color=Blue

| | `Shape` |

Filename of the 3D model which will be used to represent the object in the 3D view. See the 3d objects documentation for more information.
Shape=Rotorcraft.Bell 206.obj

| | `Debug` |

Debug text visible in the 3D view when Tacview is launched with the /Debug:on command line argument.
Debug=ObjectHandle:0x237CB9

| | `Label` |

Free real-time text displayable in the 3D view and telemetry windows (to provide miscellaneous info to the end-user)
Label=Lead aircraft

| | `FocusedTarget` |

Target currently focused by the object (typically used to designate laser beam target object, can also be used to show what the pilot is currently focused on)
FocusedTarget=3001200

| |

LockedTarget to
LockedTarget9

|

Primary target hexadecimal id (could be locked using any device, like radar, IR, NVG, ...)
LockedTarget2=3001200

| **Numeric Properties** | Property Name | Unit | Meaning | | --------------------------------------------------------------------------------------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Importance` | ratio |

The higher the ratio, the more important the object is (e.g. locally simulated aircraft could be 1.0).
Importance=1

| | `Slot` | index |

Plane position in its Group (the lowest is the leader).
Slot=0

| | `Disabled` | boolean |

Specifies that an object is disabled (typically out-of-combat) without being destroyed yet. Useful for combat training and shot logs.
Disabled=1

| | `Visible` | ratio |

Hide/show object in 3D view. 1 = fully visible. 0 = invisible (may be omitted from object lists).
Visible=0.333

| | `Health` | ratio |

Current health status. 1.0 = brand new, 0.0 = destroyed/out of combat. Does not automatically trigger events.
Health=0.84

| | `Length` | m |

Object length (useful for buildings).
Length=20.5

| | `Width` | m |

Object width (useful for buildings).
Width=10.27

| | `Height` | m |

Object height (useful for buildings).
Height=4

| | `Radius` | m |

Bounding sphere radius. Can define explosion/smoke radius. Can be animated.
Radius=82

| | `IAS` | m/s |

Indicated airspeed.
IAS=69.4444

| | `CAS` | m/s |

Calibrated airspeed.
CAS=250

| | `TAS` | m/s |

True airspeed.
TAS=75

| | `Mach` | ratio |

Mach number.
Mach=0.75

| | `AltimeterSetting` | hPa |

Current altimeter barometric setting.
AltimeterSetting=1013.2

| | `OnGround` | boolean |

Indicates aircraft ground contact.
OnGround=1

| | `AOA` | deg |

Angle of attack.
AOA=15.7

| | `AOS` | deg |

Angle of sideslip.
AOS=5.2

| | `AGL` | m |

Altitude above ground level.
AGL=1501.2

| | `HDG` | deg |

Aircraft heading (true). Used when roll/pitch unavailable.
HDG=185.3

| | `HDM` | deg |

Aircraft magnetic heading.
HDM=187.3

| | `Throttle` / `Throttle2` | ratio |

Engine throttle handle position (can be >1 for afterburner).
Throttle=0.75

| |

EngineRPM
EngineRPM2

| RPM |

Engine speed in revolutions per minute.
EngineRPM=1500

| | `NR` / `NR2` | ratio |

Normalized rotor speed (0.0–1.1 typical).
NR=0.9

| |

RotorRPM
RotorRPM2

| RPM |

Rotor rotation speed.
RotorRPM=320

| | `Afterburner` | ratio |

Afterburner status.
Afterburner=1

| | `AirBrakes` | ratio |

Air brakes status.
AirBrakes=0

| | `Flaps` | ratio |

Flaps position.
Flaps=0.4

| | `LandingGear` | ratio |

Landing gear status.
LandingGear=1

| | `LandingGearHandle` | ratio |

Landing gear handle position.
LandingGearHandle=0

| | `Tailhook` | ratio |

Arresting hook status.
Tailhook=1

| | `Parachute` | ratio |

Parachute status (not DragChute).
Parachute=0

| | `DragChute` | ratio |

Drogue/drag chute status.
DragChute=1

| | `FuelWeight` to `FuelWeight9` | kg |

Fuel quantity in tanks (up to 10).
FuelWeight4=8750

| | `FuelVolume` to `FuelVolume9` | l |

Fuel volume in tanks (up to 10).
FuelVolume=75

| | `FuelFlowWeight` to `FuelFlowWeight8` | kg/hour |

Fuel flow per engine (up to 8).
FuelFlowWeight2=38.08

| | `FuelFlowVolume` to `FuelFlowVolume8` | l/hour |

Fuel flow per engine (up to 8).
FuelFlowVolume2=53.2

| | `RadarMode` | number |

Radar mode (0 = off).
RadarMode=1

| | `RadarAzimuth` | deg |

Radar azimuth relative to aircraft.
RadarAzimuth=-20

| | `RadarElevation` | deg |

Radar elevation relative to aircraft.
RadarElevation=15

| | `RadarRoll` | deg |

Radar roll relative to aircraft.
RadarRoll=-45

| | `RadarRange` | m |

Radar scan range.
RadarRange=296320

| | `RadarHorizontalBeamwidth` | deg |

Radar azimuth beamwidth.
RadarHorizontalBeamwidth=40

| | `RadarVerticalBeamwidth` | deg |

Radar elevation beamwidth.
RadarVerticalBeamwidth=12

| | `LockedTargetMode` | number |

Primary lock mode (0 = none).
LockedTargetMode=1

| | `LockedTargetAzimuth` | deg |

Primary target azimuth.
LockedTargetAzimuth=14.5

| | `LockedTargetElevation` | deg |

Primary target elevation.
LockedTargetElevation=0.9

| | `LockedTargetRange` | m |

Primary target distance.
LockedTargetRange=17303

| | `EngagementMode` | number |

Enable/disable engagement range (0 = off).
EngagementMode=1

| | `EngagementRange` | m |

Engagement radius displayed in 3D view.
EngagementRange=2500

| | `VerticalEngagementRange` | m |

Optional vertical engagement range (ovoid bubble).
VerticalEngagementRange=1800

| |

RollControlInput
PitchControlInput
YawControlInput

| ratio |

Raw HOTAS/Yoke input.
PitchControlInput=0.41

| |

RollControlPosition
PitchControlPosition
YawControlPosition

| ratio |

Simulated cockpit control position.
PitchControlPosition=0.3

| |

RollTrimTab
PitchTrimTab
YawTrimTab

| ratio |

Trim tab position.
PitchTrimTab=-0.15

| |

AileronLeft
AileronRight
Elevator
Rudder

| ratio |

Control surface positions.
Elevator=0.15

| |

LocalizerLateralDeviation
GlideslopeVerticalDeviation

| m |

Distance from runway centerline/descent path (left/below negative).
GlideslopeVerticalDeviation=52

| |

LocalizerAngularDeviation
GlideslopeAngularDeviation

| deg |

Angular deviation from centerline/path.
LocalizerAngularDeviation=0.23

| |

PilotHeadRoll
PilotHeadPitch
PilotHeadYaw

| deg |

Pilot head orientation.
PilotHeadPitch=12

| |

PilotEyeGazePitch
PilotEyeGazeYaw

| deg |

Eye orientation relative to head.
EyeGazePitch=-15

| |

VerticalGForce
LongitudinalGForce
LateralGForce

| g |

Acceleration in aircraft axes.
VerticalGForce=3.4

| | `QNH` | hPa |

Regional barometric setting for MSL altitude.
QNH=1013.25

| |

WindDirection
WindPitch

| deg |

Wind direction (true north) and pitch.
WindDirection=45

| | `WindSpeed` | m/s |

Wind speed magnitude.
WindSpeed=12.5

| | `TriggerPressed` | boolean |

Weapon trigger state (1.0 = fully pressed).
TriggerPressed=1

| | `ENL` | ratio |

Environmental Noise Level (0–1).
ENL=0.02

| | `HeartRate` | number |

Heart rate in BPM.
HeartRate=72

| | `SpO2` | ratio |

Blood oxygen saturation percentage.
SpO2=0.95

| **Object Types (aka Tags)** Object types are now defined using a free combination of tags. The more tags, the more accurately an object is defined. Tags are separated by the plus sign +. Here are some examples: | Object Kind | Type (Tags) | | ---------------- | ------------------------------------------- | | Aircraft Carrier | `Type=Heavy+Sea+Watercraft+AircraftCarrier` | | F-16C | `Type=Medium+Air+FixedWing` | | Bicycle | `Type=Light+Ground+Vehicle` | | AIM-120C | `Type=Medium+Weapon+Missile` | | Waypoint | `Type=Navaid+Static+Waypoint` | Here is the list of currently supported tags. Tacview will use them for display and analysis purposes. | Use | Tags | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Class |

Air
Ground
Sea
Weapon
Sensor
Navaid
Misc

| | Attributes |

Static
Heavy
Medium
Light
Minor

| | Basic Types |

FixedWing
Rotorcraft
Armor
AntiAircraft
Vehicle
Watercraft
Human
Biologic
Missile
Rocket
Bomb
Torpedo
Projectile
Beam
Decoy
Building
Bullseye
Waypoint

| | Specific Types |

Tank
Warship
AircraftCarrier
Submarine
Infantry
Parachutist
Shell
Bullet
Grenade
Flare
Chaff
SmokeGrenade
Aerodrome
Container
Shrapnel
Explosion

| Here are the recommended common types (combination of tags) you should use to describe most of your objects for display in Tacview 1.x: | Type | Tags | | ---------------- | -------------------------------------------- | | Plane | `Air + FixedWing` | | Helicopter | `Air + Rotorcraft` | | Anti-Aircraft | `Ground + AntiAircraft` | | Armor | `Ground + Heavy + Armor + Vehicle` | | Tank | `Ground + Heavy + Armor + Vehicle + Tank` | | Ground Vehicle | `Ground + Vehicle` | | Watercraft | `Sea + Watercraft` | | Warship | `Sea + Watercraft + Warship` | | Aircraft Carrier | `Sea + Watercraft + AircraftCarrier` | | Submarine | `Sea + Watercraft + Submarine` | | Sonobuoy | `Sea + Sensor` | | Human | `Ground + Light + Human` | | Infantry | `Ground + Light + Human + Infantry` | | Parachutist | `Ground + Light + Human + Air + Parachutist` | | Missile | `Weapon + Missile` | | Rocket | `Weapon + Rocket` | | Bomb | `Weapon + Bomb` | | Projectile | `Weapon + Projectile` | | Beam | `Weapon + Beam` | | Shell | `Projectile + Shell` | | Bullet | `Projectile + Bullet` | | Ballistic Shell | `Projectile + Shell + Heavy` | | Grenade | `Projectile + Grenade` | | Decoy | `Misc + Decoy` | | Flare | `Misc + Decoy + Flare` | | Chaff | `Misc + Decoy + Chaff` | | Smoke Grenade | `Misc + Decoy + SmokeGrenade` | | Building | `Ground + Static + Building` | | Aerodrome | `Ground + Static + Aerodrome` | | Bullseye | `Navaid + Static + Bullseye` | | Waypoint | `Navaid + Static + Waypoint` | | Container | `Misc + Container` | | Shrapnel | `Misc + Shrapnel` | | Minor Object | `Misc + Minor` | | Explosion | `Misc + Explosion` | ### Comments To help you during the debugging process of your exporter, it is possible to comment any line of the file by prefixing them with the double slash // like in C++. ``` // This line and the following are commented // 3000102,T=41.6251307|41.5910417|2000.14,Name=C172 ``` These lines will be ignored by Tacview when loading the file. Comments are not preserved. You will notice that they are discarded the next time you save the file from Tacview. If you want to include debug information which is preserved, you can use the dedicated `Debug` `Event` described earlier in the global properties. Because of loading performance considerations, it is only possible to insert a comment at the beginning of a line.