Vyrtuoz

Yes, if the information can be exported. This kind of data will be visible in Tacview (even if displayed in a different way than in DCS World) after the second iteration on the new exporter (which is in its first iteration).

Tacview 1.5.2 is available You can now download Tacview 1.5.2 which introduces a few fixes while waiting for the next major upgrade: http://tacview.net/download/ Amongst other things, this version fixes a crash in the LUA data exporter with DCS World 1.5.5. I am still working on the new exporter and I hope to be able to release a beta version by the end of the year.

New export script v1.5.2 Tacview 1.5.1 export script is not working with the latest beta version of DCS World. So, I have published a fix in Tacview 1.5.2 beta 1: http://www.tacview.net/download/beta/ If you do not have a license to use beta versions of Tacview you can manually install the latest script by follow the instructions provided in the documentation: http://www.tacview.net/documentation/dcs/#q14 http://www.tacview.net/download/TacviewExportDCS.lua

I will add an anti-cheat option so the host of the game can decide if the clients can record or not the flight in progress. Clients will not be able to export data without prior approval of the server. Another option will enable the host to create a file for each client, so each squadron member can get his/her file after the flight (assuming your server can share files). I will discuss further the new options as soon as the new exporter is working enough. Tacview command line options will not change. Also, all the exported files will already be optimized and compressed, so it will not be necessary anymore to use Tacview command line to do so after each flight for example.

About the new flight recorder New Exporter Comming Soon As announced a few days ago on Twitter, I have resumed my work on the new Tacview exporter for DCS World. What have changed during the past 10 years? Battlefields are much busier. Thousand ground and air units are common these days. DCS World can export much more data than ever. Tacview has evolved a lot too and can now manage any kind of data, in astronomical amount, and soon in real-time! What’s wrong with the current exporter? The current LUA exporter is now 10 years old. Even if it is working fine, it needs a rejuvenation cure for the following reasons: Made of LUA script, it is not as fast as I would like, especially with overcrowded battlefields. For example, the current export script can take up to 10% of CPU. Because of LUA, many programming features are not available or very complicated/slow to code: For example, it is not possible to compress the exported data. DCS World is now offering an extended API which offers much more possibilities than 10 years ago. For example, it should now be possible to export mission data like waypoints. What about the new exporter? The new exporter will be 100% made of C++. Which means that is it going to be as fast and powerful as possible is can be. Deeply optimized and multithreaded the new exporter will take less than 1% of CPU. Please note that this exclude DCS World LoGetWorldObjects() bug explained bellow. Data export frequency and resolution will be tweaked to both same storage space and gives more accurate replays. The created files will be already optimized and compressed. No need to re-save your files from Tacview anymore! An efficient network connection will be possible between DCS World exporter and Tacview so you can see a battlefield evolving in real-time. An anti-cheat system will be implemented so you can delay data review to prevent people from spying your network session while still enabling data export for later debriefing. All cockpit available data will be exported and will be displayable in Tacview telemetry windows and in the HUD view. Feel free to post any remarks, questions and suggestions on this thread. About DCS World export performance issue: DCS World LoGetWorldObjects() currently takes about 20% of CPU. This is a bug which can only be fixed by ED dev team. There is nothing we can do on Tacview site do fix this performance issue. For example: This is the most important export function and we must call it at least once a frame to know what is going on. Because without it, it is not possible to know which objects have been created/deleted/updated. With Tacview 1.5.1 you can check your DCS.log file after a mission to see by how much CPU Tacview LUA exporter and LoGetWorldObjects() are taking to export data. For instance, they are respectively taking: Tacview LUA script AddUpdateObjects(): 10% CPU (Tacview side, will be fixed) DCS World LoGetWorldObjects(): 20% CPU (ED dev team side) 02995.954 INFO LuaExport::LuaExportStart: [Tacview.UpdateLog] Profile Time=[30.0s] Frame Rate=[30.9 fps] w/o Export=[44.7 fps] DCS Ratio=[69.0%] Export Ratio=[31.0%] 02995.954 INFO LuaExport::LuaExportStart: -------- Profiled Section -------- | CallCount | Ratio | Total | 02995.954 INFO LuaExport::LuaExportStart: AddUpdateObjects(ballistic) | 926 | 0.1% | 0.0% | 02995.954 INFO LuaExport::LuaExportStart: AddUpdateObjects(units) | 926 | 31.2% | 9.7% | 02995.954 INFO LuaExport::LuaExportStart: LoGetWorldObjects(ballistic) [C++] | 926 | 0.4% | 0.1% | 02995.954 INFO LuaExport::LuaExportStart: LoGetWorldObjects(units) [C++] | 926 | 67.4% | 20.9% | 02995.954 INFO LuaExport::LuaExportStart: RemoveObjects | 926 | 0.6% | 0.2% |

Thank you very much Gliptal, this is nice of you! I’m going to add your Tornado to Tacview 1.5.2 so everyone can enjoy it soon.

Indeed, the tool to create or edit objects does not send data over the network. I have to create it quickly for local debriefing. I will need more time to make it work nicely with the online debriefing. Meanwhile, you may add the object (bullseye) in an empty world and share the tiny resulting file with your mates so they can merge it with their own data.

Nice work Gliptal! Like video games Tacview supports one sided triangles only. So you have to make sure your triangles are properly oriented in Blender (counter clock wise). Try to export your object with the following options: File -> Export OBJ -> No Normals / No UVs / No Materials / Triangulate Faces -> -Z forward / Y Up Then reload it in Blender and make sure faces are displayed one sided only. This should show which ones have the wrong orientation so you can “invert” them the proper way.

Thank you for the offer Gliptal. The 3D models format is documented here: http://www.tacview.net/documentation/3dobjects/en/ I may contact you later if I need additional 3d models after the upgrade currently in progress.

@Gliptal Thank you for the data, I'm going to check this for the next version @BaD CrC Not yet. I'm currently try to acquire more 3D models. Let's hope the SA342 will be one of them...

It looks like that, for some reason, the download is not complete. Can you try from another mirror, especially the last one (called free) to see if it works better? You may also want to try with another web browser like edge, firefox, chrome. Or from one of your friends computer. You can find alternate download sources from here: http://www.tacview.net/download/latest/

Can you bookmark some of the units which are not working (using the bookmark button in the playback toolback of Tacview) and share me the resulting .zip.acmi file? I will check what is going on.

You can double click on floating windows title to dock them. Or, in the worst case, you can reset everything by deleted the registry entry: [HKEY_CURRENT_USER\SOFTWARE\Stra Software\Tacview]

Sure! Even if the best would be an improvement of DCS World export interface, I will not release this feature until I have found a graceful way to prevent cheating as much as possible.

Tacview 1.5.1 Tacview 1.5.1 is available! http://tacview.net/download/ First, I want to thank all of you for your feedback. It was invaluable to pinpoint and fix new telemetry engine bugs. There are quite a lot of important improvements in this new release: All reported bugs related to the telemetry have been fixed. You can now create and edit objects (like bullseye) directly from the tool menu. Now the HUD clearly display IAS/CAS and magnetic heading when available. Falcon 4 time zones have been added for all major theaters: day, night and sun position are now correct. Added support for X-Plane 9/10, 32-bit and 64-bit. FSX/Prepar3D flight data recorder as been fully rewritten to generate more accurate data and up to 5 times smaller acmi files. Now, I know that not all of you are interested in FSX and X-Plane... However, everyone will benefit from the work which has just been accomplished. I have created from scratch an universal exporter. Because they are very easy to work with, FSX and X-Plane were used as efficient testbeds for it. Now it has been debugged and optimized, I will be able to use it to create a brand new real-time data exporter for DCS World and, maybe later, a real-time exporter for Falcon 4… Before doing that, the next step is to rewrite a part of Tacview graphical user interface so it can gracefully handle real-time data change and recording. As soon as this work is complete, I will be able to create real-time data exporters. And whenever I will make an improvement, tweak, or a fix in this universal exporter, all supported flight simulations will automatically benefit from it! FEATURES & CHANGES X-Plane is now natively supported thanks to the XPL2ACMI plugin FSX2ACMI has been rewritten to be more accurate and to generate acmi 2.0 files 5x smaller than before New ACMI 2.1 file format which is up to 10% smaller thanks to longitude/latitude median reference point You can now add objects to the world directly from Tacview tools menu You can now edit core object properties directly from Tacview tool menu CAS is now displayed in HUD view when proper data is available and IAS is not available The type of speed available in HUD view is now explicitly displayed Magnetic heading is now displayed in HUD view when available Added support for TimeZone offset for Falcon 4.0 theaters Added an option to display labels only for selected objects Using shorter notation for telemetry in labels to reduce clutter DCS World dummy pilots and units names are not exported anymore to reduce clutter FIXES CAS was not properly calculated when only spherical coordinates were available Merging a DTC file with VHS was often removing objects from the battlefield Fixed local and UTC time for Falcon 4.0 theaters (this fixes the sun position and sky color) Advanced telemetry AOA was not properly exported (in radian instead of degrees) Invalid time displayed in raw telemetry when loading a file from a different telemetry source XML flight log was listing objects colors instead of coalitions names Fixed small memory leak related to objects without data Remove bookmark command was not working for real Tacview now properly offers the zip.acmi file format when using the “Save As” command Multimedia keys were mistakenly intercepted (they are now available to your favorite music player) Increate about dialog box size to accommodate some foreign languages

Real-time flight data recording and analysis is not yet available. A first version is planned in the coming releases of Tacview 1.5.x. Which use are you planning for this feature?

Dart is right: the best way to connect DCS World with an external application right now is in the export.lua. You can find samples in the official file: C:\Program Files\Eagle Dynamics\DCS World\Scripts\Export.lua However, whenever you will be ready to code in this file, do it in the following folder to be clean (DCS World will load the user export.lua at each mission startup): C:\Users\[Your Name]\Saved Games\DCS\Scripts\Export.lua You should be able to get all the data you have listed for the player aircraft. However, AI and network aircraft export will expose only few data like position/rotation and name. Also, keep in mind, that, during network session, the server can disable export capabilities to prevent cheating. In that case, your program may not work (like Tacview). Anyway this should be more than enough data to start working on prototypes and will probably work fine in most of the cases.

Guess what? I the media keys were still intercepted by Tacview, I forgot a case… This is fixed in Tacview 1.5.1 (I have validated against the Windows 10 TV&Movies app)

This is strange, because there is no audio at all (yet) in Tacview. Anyway, I’m glad you found the solution!

JorgeIII, This is strange, because I’m developing using the latest official version of Windows and I didn’t notice any issue between the anniversary update and Tacview (and I don’t see how it could be otherwise). Can you check the following check list? http://www.tacview.net/support/reportbug/ To help you I need more information: Can you share me your dxdiag log file (like explained on the support page)? Also, if Tacview crashes, you should see a dialog box inviting you to share a mini-dump file which will help me to see where it has crashed.

I understand. This is a bit early to work on this point, but when I will do, I will certainly contact Ciribob to work on a compatible solution with him.

Synchronized video and audio playback are planned and should be available this year. However, I do not plan to provide audio or video recorders because there is already plenty of tools for that and I'm sure you will prefer me to work on more flight specific tools like real-time flight recording ;)

Yes, I will try to export the waypoints when I will rewrite the exporter for DCS World.

I see! I have fixed the bug in Tacview 1.5.1. To sum up: When using the command line to convert files, by default, Tacview already saves your files in the .zip.acmi file format instead of .txt.acmi. You can override this behavior by specifying an explicit output name like [myflightdata.txt.acmi], if you just want to clean up the file without compressing it for example… When using the File|Save option from the GUI, Tacview 1.5.1 now properly offers to save your file in the .zip.acmi file format instead of “just” .txt.acmi if your source file was not an acmi 2.0 file. (which is the case for current DCS World flight data)

To be honest with you, the optimizations done are for in-memory (RAM) data, not on your storage device yet. In the coming versions, I will rewrite DCS World exporter. It will save less data, in a packed file, so you will not need any more to compress your files using the command line after each flight. I’m rewriting Tacview modules progressively to reduce the risk of breaking things up…