Tacview - Revision history

Nanne118: Page expanded massively

2018-12-18T22:17:59Z

Page expanded massively

Show changes

Nanne118: /* Interface Overview */

2018-12-18T20:50:50Z

‎Interface Overview

Nanne118 at 01:32, 14 October 2018

2018-10-14T01:32:50Z

Nanne118 at 01:32, 14 October 2018

2018-10-14T01:32:19Z

Nanne118: /* Interface Overview */

2018-10-14T01:31:42Z

‎Interface Overview

Nanne118: /* Tacview interface */

2018-10-14T01:24:45Z

‎Tacview interface

Nanne118: /* Tacview interface */

2018-10-14T01:24:13Z

‎Tacview interface

Nanne118: /* Tacview setup */

2018-10-14T01:15:32Z

‎Tacview setup

Nanne118 at 01:10, 14 October 2018

2018-10-14T01:10:22Z

Nanne118 at 01:02, 14 October 2018

2018-10-14T01:02:47Z

← Older revision		Revision as of 20:50, 18 December 2018
Line 51:		Line 51:
	=== Interface Overview ===		=== Interface Overview ===

−	[[File:Tacview_UI.png\|~~center~~\|~~1000px~~]]	+	[[File:Tacview_UI.png\|right\|700px]]
		+
		+	{\| class="wikitable"
		+	! colspan="3" style="text-align: center; background-color:#f8a102;" \| Tacview overview
		+	\|-
		+	\| style="text-align: center;" \| #
		+	\| Function
		+	\| Details
		+	\|-
		+	\| style="text-align: right; background-color:#accf40;" \| 1
		+	\| style="background-color:#accf40;" \| File operations
		+	\| style="background-color:#accf40;" \| Open, save, merge, export tracks
		+	\|-
		+	\| style="text-align: right;" \| 2
		+	\| Online debriefing
		+	\| You can connect multiple clients together to debrief your flight together
		+	\|-
		+	\| style="text-align: right; background-color:#accf40;" \| 3
		+	\| style="background-color:#accf40;" \| Visible windows / tools
		+	\| style="background-color:#accf40;" \| Hide / show telemetry windows, charts and media (videos)
		+	\|-
		+	\| style="text-align: right;" \| 4
		+	\| Manipulate objects
		+	\| Editing object properties, time shifting
		+	\|-
		+	\| style="text-align: right; background-color:#accf40;" \| 5
		+	\| style="background-color:#accf40;" \| Scripts and addons
		+	\| style="background-color:#accf40;" \| LSO Bot, AoA Indexer, lua scripting
		+	\|-
		+	\| style="text-align: right;" \| 6
		+	\| TacView Settings
		+	\| Language, imperial/metric, terrain selection, position format
		+	\|-
		+	\| style="text-align: right; background-color:#accf40;" \| 7
		+	\| style="background-color:#accf40;" \| Help page(s)
		+	\| style="background-color:#accf40;" \| Access list of commands, command line syntax, check for upgrades
		+	\|-
		+	\| style="text-align: right;" \| 8
		+	\| 1st Selected Contact
		+	\| Select first of two contacts to compare (against the second contact): typically own plane
		+	\|-
		+	\| style="text-align: right; background-color:#accf40;" \| 9
		+	\| style="background-color:#accf40;" \| Contact relationship
		+	\| style="background-color:#accf40;" \| Type of relationship between selected contacts: Range/aspect, Range/bearing, Range/Rate of closure
		+	\|-
		+	\| style="text-align: right;" \| 10
		+	\| View relationship
		+	\| How do you view the relationship: Centered or look at target
		+	\|-
		+	\| style="text-align: right; background-color:#accf40;" \| 11
		+	\| style="background-color:#accf40;" \| 2nd Selected Contact
		+	\| style="background-color:#accf40;" \| Select second of two contacts to compare (against the first contact): typically target (vehicle / plane)
		+	\|-
		+	\| style="text-align: right;" \| 12
		+	\| Telemetry 1st Contact
		+	\| View list of 1st contact telemetry (typically 1st contact selected is own plane)
		+	\|-
		+	\| style="text-align: right; background-color:#accf40;" \| 13
		+	\| style="background-color:#accf40;" \| Telemetry 2nd Contact
		+	\| style="background-color:#accf40;" \| View list of 2nd contact telemetry (typically 2nd contact selected is target)
		+	\|-
		+	\| style="text-align: right;" \| 14
		+	\| Flight log
		+	\| List of events that happened in this flight
		+	\|-
		+	\| style="text-align: right; background-color:#accf40;" \| 15
		+	\| style="background-color:#accf40;" \| Playback controls
		+	\| style="background-color:#accf40;" \| Play, Fast Forward, shows HUD view, show SAM range
		+	\|}

← Older revision		Revision as of 01:32, 14 October 2018
Line 41:		Line 41:

	The configurable delay (which can be set in the Tacview settings within the DCS settings) allow you as a server host to prevent people from livestreaming their data to their Tacview client and using it to cheat, whilst allowing people to export the Tacview data with a delay to use for their own evaluation and feedback. This option is server authoritative, meaning that if the server host does not have Tacview installed / enabled the playback delay will automatically be set to the default 10 minutes delay: this only works if the server host has not been lazy and outright disabled the data export.		The configurable delay (which can be set in the Tacview settings within the DCS settings) allow you as a server host to prevent people from livestreaming their data to their Tacview client and using it to cheat, whilst allowing people to export the Tacview data with a delay to use for their own evaluation and feedback. This option is server authoritative, meaning that if the server host does not have Tacview installed / enabled the playback delay will automatically be set to the default 10 minutes delay: this only works if the server host has not been lazy and outright disabled the data export.
		+

	== Tacview Interface ==		== Tacview Interface ==

← Older revision		Revision as of 01:32, 14 October 2018
Line 50:		Line 50:
	=== Interface Overview ===		=== Interface Overview ===

−	[[File:Tacview_UI.png\|center]]	+	[[File:Tacview_UI.png\|center\|1000px]]

← Older revision		Revision as of 01:31, 14 October 2018
Line 49:		Line 49:

	=== Interface Overview ===		=== Interface Overview ===
		+
		+	[[File:Tacview_UI.png\|center]]

@@ Line 42: / Line 42: @@
 The configurable delay (which can be set in the Tacview settings within the DCS settings) allow you as a server host to prevent people from livestreaming their data to their Tacview client and using it to cheat, whilst allowing people to export the Tacview data with a delay to use for their own evaluation and feedback. This option is server authoritative, meaning that if the server host does not have Tacview installed / enabled the playback delay will automatically be set to the default 10 minutes delay: this only works if the server host has not been lazy and outright disabled the data export.
-== Tacview interface ==
+== Tacview Interface ==
 Without having a flight recording loaded up the interface of Tacview looks quite bare, but this changes as soon as you load up a recorded flight recording. You can load up a flight recording by clicking the top left USB icon and select a flight recording from a previous flight you have performed: files are saved by default in the path (flight recording save path can be changed within Tacview)
   \My Documents\Tacview\
 Flight recordings are of the .acmi format and are compressed into a .zip by default to save on hard drive storage space; if the DCS settings Tacview section you can alter the compression desired for the .acmi files.

← Older revision		Revision as of 01:24, 14 October 2018
Line 43:		Line 43:

	== Tacview interface ==		== Tacview interface ==
		+
		+	Without having a flight recording loaded up the interface of Tacview looks quite bare, but this changes as soon as you load up a recorded flight recording. You can load up a flight recording by clicking the top left USB icon and select a flight recording from a previous flight you have performed: files are saved by default in the path (flight recording save path can be changed within Tacview)
		+	\My Documents\Tacview\
		+	Flight recordings are of the .acmi format and are compressed into a .zip by default to save on hard drive storage space; if the DCS settings Tacview section you can alter the compression desired for the .acmi files.

← Older revision		Revision as of 01:15, 14 October 2018
Line 37:		Line 37:

	Please note that some servers have disabled data export, as it can be used as a form of cheating to observe where enemy units are located by spectating the live feed that DCS is generating in Tacview. Although there is delay option available to server owners to mitigate this issue (releasing the data only after a configurable delay in minutes), some servers still not feel comfortable allowing this data export. A way around this is to watch the track (.trk) file that DCS automatically generates for any flight: after watching this track and allowing some additional time (for your computer / client loading into the multiplayer server, as well as quitting) the replay should be available in Tacview.		Please note that some servers have disabled data export, as it can be used as a form of cheating to observe where enemy units are located by spectating the live feed that DCS is generating in Tacview. Although there is delay option available to server owners to mitigate this issue (releasing the data only after a configurable delay in minutes), some servers still not feel comfortable allowing this data export. A way around this is to watch the track (.trk) file that DCS automatically generates for any flight: after watching this track and allowing some additional time (for your computer / client loading into the multiplayer server, as well as quitting) the replay should be available in Tacview.
		+
		+	=== Playback delay for server hosting ===
		+
		+	The configurable delay (which can be set in the Tacview settings within the DCS settings) allow you as a server host to prevent people from livestreaming their data to their Tacview client and using it to cheat, whilst allowing people to export the Tacview data with a delay to use for their own evaluation and feedback. This option is server authoritative, meaning that if the server host does not have Tacview installed / enabled the playback delay will automatically be set to the default 10 minutes delay: this only works if the server host has not been lazy and outright disabled the data export.

	== Tacview interface ==		== Tacview interface ==

← Older revision		Revision as of 01:10, 14 October 2018
Line 35:		Line 35:
	When installing Tacview it should automatically be able to detect and recognize DCS, after which Tacview will function as a module inside of DCS. This also means Tacview get its own settings page within the DCS settings, from which you can adjust and tweak the various options		When installing Tacview it should automatically be able to detect and recognize DCS, after which Tacview will function as a module inside of DCS. This also means Tacview get its own settings page within the DCS settings, from which you can adjust and tweak the various options
	offered: one such notable option that should be enabled by default is that Tacview records the flights you perform in DCS. You can also alter settings like the Bookmark keybind (used to mark important events during your flight to view back later), the compression level (to crank down on the file sizes) and the profiling period (how often data is written to the dcs.log file).		offered: one such notable option that should be enabled by default is that Tacview records the flights you perform in DCS. You can also alter settings like the Bookmark keybind (used to mark important events during your flight to view back later), the compression level (to crank down on the file sizes) and the profiling period (how often data is written to the dcs.log file).
		+
		+	Please note that some servers have disabled data export, as it can be used as a form of cheating to observe where enemy units are located by spectating the live feed that DCS is generating in Tacview. Although there is delay option available to server owners to mitigate this issue (releasing the data only after a configurable delay in minutes), some servers still not feel comfortable allowing this data export. A way around this is to watch the track (.trk) file that DCS automatically generates for any flight: after watching this track and allowing some additional time (for your computer / client loading into the multiplayer server, as well as quitting) the replay should be available in Tacview.
		+
		+	== Tacview interface ==

@@ Line 6: / Line 6: @@
 |height = 90px
 }}</center>
 {{OtherModuleInfo
@@ Line 15: / Line 14: @@
 }}
-TacView is a third party program that records flight/telemetry information about every vehicle in a mission, and features a playback engine to allow you to get a "godmode" view of every event that occurred during a mission. TacView is enormously useful because it allows you to review your played missions from the "godmode" perspective, which allows you to determine what went wrong or right during your flights: if you for example think you just died out of nothing, TacView can help you by reviewing your 'track' (a recording of your flight) and for example tell you it was that sneaky Russian SU-27 that killed you with a heatseeker.
+Tacview is a free third party program that hooks into DCS (kinda like a module) that records and allows you to replay all manner of flight characteristics (flight / telemetery data) and information you have encountered during our flight. It is particularly useful because it records the entire flight: not only does it record your own data, it also records all the data of friendly and enemy contacts you have encountered. It is also compatible with X-Plane, Falcon 4 (BMS), IL-2 and a handful of other flight simulators.
-From their site:
+__TOC__
-''"Eager to understand what really happened during your last flight? Tacview is a universal flight data analysis tool which enables you to easily record, analyze and understand any flight to improve your skills much faster than with conventional debriefings."''
+== Tacview versions ==
-[http://www.tacview.net Tacview's official site] has detailed information about installing TacView for a variety of different sim (it also works for X-Plane, Falcon 4, and a handful of others!).
+[https://www.tacview.net/features/comparison/en/ The purchasable TacView Standard and Advanced editions offer some advanced functionality], but most of this functionality is rarely needed by the standard pilot. Functionality offered in these editions includes more advanced telemetry support (being able to indicate systems such as the gear position and the radar display; showing which target was being locked), as well as support for online debriefing which allows groups to do their debriefings together. Most importantly of course is that these paid versions offer support to the developer(s) of this amazing software!
-[[File:TacView Screen.jpg|thumb|350px|The TacView interface]]
+== Tacview setup ==
-'''Installation'''
+Installing Tacview is easy and painless, as you can just obtain the .exe installer from their website (listed in the sidebar). There is a little more effort required into getting familiar with the user interface and setting up a multiplayer environments to debrief your entire flight at once, but [http://www.tacview.net/documentation/dcs/en/ Tacview's DCS installation guide] is a great help for more difficult tasks, such as how to import terrain into Tacview.
-[http://www.tacview.net/documentation/dcs/en/  Tacview's DCS installation guide] will get you setup, single player setup is relatively simple, if you plan on hosting multiplayer servers make sure you read that link thoroughly to ensure that other players can record their data when flying on your server.
+When installing Tacview it should automatically be able to detect and recognize DCS, after which Tacview will function as a module inside of DCS. This also means Tacview get its own settings page within the DCS settings, from which you can adjust and tweak the various options