Hello and welcome to the VTOL VR Tacview Data Logger mod!
It's been long time in the making and a fairly significant undertaking for me. The Tacview data log allows players to record their flights in real time and save all enemy, allied and player vehicle flight data. The data log (in ACMI format) can then be opened within the Tacview software for review, tactical analysis and determination as to why exactly the carrier did not clear you to land!
Just a couple of notes to start off with. I'm not a game developer and I don't work in C#, so I may have taken some shortcuts. I'm well aware this mod is not as well optimized as it could and should be. On large maps with numerous actors this mod could introduce significant lag as it loops through and collects all the necessary data. Future iterations will be able to handle this a bit better.
Example flight (2v2) on Akutan
Highlighting the various Tacview models
Fox 2! Showing off the flares and missile tracking
Even supports bombing runs!
Rolling scissors with an ASF-33.
So thats why I wasn't cleared for a conventional landing...
To use the mod simply install the mod, launch the game, and enable the mod. At the time of writing it is important that you enable the mod every time you start the game. Once you begin a flight scene the data logger will automatically begin recording, as of now there is no positive indication of the recording in flight.
This mod will be available for download on https://vtolvr-mods.com (Insert direct link when uploaded). I would recommend using the One-Click Install function to automatically download the mod.
Alternatively you can download the latest release here: https://github.com/nebriv/VTOLVR-TacviewLogger/releases/latest
If you are manually installing you need to place the downloaded zip file in your VTOL VR Game folder inside the VTOLVR_ModLoader\mods\ directory. The mod loader should automatically detect and unzip it for you once launched.
To use the mod simply launch the game via the mod loader (open the mod loader and press play). Once in game, after you click start you should see a "Mods" button. Open the mods page, select the Tacview Data Logger and click load. You should be good to go! At the start of the first few missions (and on those of particular importance) I would recommend browsing to the TacViewDataLogs folder within the VTOL VR game folder, and making sure you see a new folder with today's date and time, in that folder should be the three files described below.
All flight recordings are stored in the VTOL VR Game Folder under TacViewDataLogs. Within this folder multiple folders with the datetime stamp of the flight will be created. Within this flight folder three files should be created. - datalog.acmi - This is the primary datalog created for viewing in Tacview. With Tacview installed, you should simply be able to double click this and open it. - customHeightMapXML.txt - This is custom XML used to display the exported heightmap. See the heightmap section below. - heightmap_MAPName.data - This is the heightmap data. Copy this file into C:\ProgramData\Tacview\Data\Terrain\Custom. See Height Maps/Terrain for more details.
All active actors (vehicles and projectiles) within a scene are logged. The following parameters are generally all logged. Some ground and water vehicles may not contain all applicable data. - AOA - IAS - Altitude - AGL - Location - Callsign/Designation
VTOL VR models can be added to Tacview via the following steps: 1. Copy the vtolvr.xml file to C:\ProgramData\Tacview\Data\Database\Default Properties 2. Copy all the .obj files from the assets folder into C:\ProgramData\Tacview\Data\Meshes
All VTOL VR models are properly of Boundless Dynamics, LLC. except the F-45 and F/A-26 Models created by F/A-26B on the VTOL VR Discord Channel.
Height maps are generally generated and exported at the start of every mission. They will be located in the mission's datalog folder. You should see customHeightMapXML.txt and heightmap_MAPNAME.data. To use this heightmap in Tacview follow the below steps. 1. If you haven't done so, copy the CustomHeightmapList.xml file from C:\Program Files (x86)\Tacview (beta)\Data\Terrain\Custom into C:\ProgramData\Tacview\Data\Terrain\Custom. 2. Copy the .data file to C:\ProgramData\Tacview\Data\Terrain\Custom. 3. Copy the contents of the customHeightMapXML.txt file (Except for "\<?xml version="1.0" encoding="utf-8"?>") into the new CustomHeightmapList.xml (C:\ProgramData\Tacview\Data\Terrain\Custom\CustomHeightmapList.xml) between the \<CustomHeightmapList> nodes. Any XML parsing errors in this file will cause Tacview to not properly load the terrain.
If you wish to report any bugs you can do so by creating a new Issue in this Github repository or you can contact me on the VTOL VR modding discord (@nebriv0001). When reporting bugs please include as much detail as possible including steps to reproduce. If possible please include your player.log file as well as your TacviewDataLogger data for the mission(s) in question.
Simply recompile with the latest version of VTOL. Thanks Mattidg and everyone else for supporting this project!
{'version': {'orig': '2.6', 'new': '2.7'}, 'user_uploaded_file': {'orig': <FieldFile: uploaded_files/ecaWpmrwmz/Tacview_Data_Logger.zip>, 'new': <FieldFile: Tacview_Data_Logger.zip>}}
- Code fixes to add preliminary support for MP - Resource updates to support latest VTOL VR version - Update to assets to include AH-94 model (Don't forget to update your assets and XMLfile as per the mod description!)
{'version': {'orig': '2.5', 'new': '2.6'}, 'user_uploaded_file': {'orig': <FieldFile: uploaded_files/3Rh9JeyrIX/Tacview_Data_Logger.zip>, 'new': <FieldFile: Tacview_Data_Logger.zip>}}
Uhhmm it also includes forgotten performance and bug fixes from a version 2.4 ghost branch. Whoops. :fingers_crossed:
{'version': {'orig': '2.4', 'new': '2.5'}, 'user_uploaded_file': {'orig': <FieldFile: uploaded_files/Cqgi0OlGnl/Tacview_Data_Logger.zip>, 'new': <FieldFile: Tacview_Data_Logger.zip>}}
You'll need to copy over the models again when updating. Thanks TytanRock for the PR!
{'version': {'orig': '2.3.1', 'new': '2.4'}, 'user_uploaded_file': {'orig': <FieldFile: uploaded_files/oo7QSk7Y8z/Tacview_Data_Logger.zip>, 'new': <FieldFile: VTOLVR-TacViewLogger.zip>}}
{'version': {'orig': '2.3', 'new': '2.3.1'}, 'user_uploaded_file': {'orig': <FieldFile: uploaded_files/qL7Vx4QCY8/Tacview_Data_Logger.zip>, 'new': <FieldFile: Tacview_Data_Logger.zip>}}
Uhh "fixed" some "bugs". So now it "works.
{'version': {'orig': '2.2', 'new': '2.3'}, 'user_uploaded_file': {'orig': <FieldFile: uploaded_files/M1MvQtD9MA/TacviewDatalogger.zip>, 'new': <FieldFile: TacviewDatalogger.zip>}}
Fixed the radar in the AV-42 from spamming the logs. Fixed the backwards orientation of some models.
{'version': {'orig': '2.1', 'new': '2.2'}, 'user_uploaded_file': {'orig': <FieldFile: uploaded_files/7xLhAC1NBf/TacviewDatalogger.zip>, 'new': <FieldFile: TacviewDatalogger.zip>}}
Fixes a modloader instance error. Fixes some reload errors where new scenes weren't being detected.
{'version': {'orig': '2.0', 'new': '2.1'}, 'user_uploaded_file': {'orig': <FieldFile: uploaded_files/2VlRQ2fubQ/TacviewDatalogger.zip>, 'new': <FieldFile: TacviewDatalogger.zip>}}