DCS WORLD PLANES UPGRADE
DCS WORLD PLANES FULL
DCS WORLD PLANES ZIP

If you go in the special options of DCS World for Tacview, you will find an option to record only the local aircraft depending on the kind of flight you are doing.

Track files are not reliable, and DCS replay can diverge from the original flight, especially if the mission is long.

The good thing about this is that you can, for example, disable Tacview exporter during your multiplayer flight, and then export the DCS *.trk file later, with the exporter enabled. As a matter of fact, it is mandatory during multiplayer games. Right now, there are several ways to mitigate this issue, while still enjoying the game.Д®xport tracks (*.trk) files recorded by DCS WorldДCS can record a track file for each of your flights. Is it possible to avoid this problem in the first place? Not only this will help with Tacview export, but this will also benefit to any add-ons such as LotAtc.

DCS WORLD PLANES UPGRADE

When I will believe I have found a clean and efficient solution, I will propose it to Eagle Dynamics so they can upgrade DCS export API. While working on Tacview 2, I am thinking about a better way of enumerating objects. That way its load would be minimal and spread over several frames. The only way to fix this would be for DCS World to offer a new API, which could be more selective, progressive, and efficient in the way objects are enumerated. On the other hand, you have the infamous LoGetWorldObjects() function: There is no way around it, it is the only way to request objects, it is not possible to split it over several frames, and it is probably the most inefficient way to enumerate a lot of objects.

DCS WORLD PLANES ZIP

On one hand you have Tacview exporter which is now fully written in multithreaded C++, it uses less than 1% of CPU on the main thread, and all the rest (such as telemetry fusion, data cleanup, zip compression, real-time telemetry over the network) is handled on background threads at a cost which is considered negligible. Unfortunately, the problem lies in the way DCS World enumerates active objects and gives them to Tacview via Lua. In the end you may notice stuttering or overall lower performance depending on your system and the size (in objects) of the mission. Because this requires a log of memory allocation/free and copy operations.

DCS WORLD PLANES FULL

That would not be a problem for the usual C++ program, but in that case, creating a full list from scratch of 10000+ samples of data going through Lua, is kind of devastating for the CPU. In this example, we can ignore bullets which are numerous but sporadic over a four-hour mission. This could easily mean more than 15000 samples of data. Imagine that each frame, via LoGetWorldObjects(), you request the full list of dynamic objects, and for each of them, their ID, name, country, detailed coordinates (such as latitude, longitude, altitudeвЂ¦), so on. How can a modern computer be so slow at enumerating a few thousand objects? I believe this comes down to the way the Lua language is working. In that case, LoGetWorldObjects() could be quite inefficient and can slow down the whole simulation. More specifically, the LoGetWorldObjects() function which gives the list of all dynamic (a well as a few static) objects currently active in the mission.ДЄll is well until you run a mission with thousands of active objects (including aircraft, SAMs, vehicles, missiles, to name a few).

To record the telemetry, Tacview uses the official Lua script interface provided by DCS World via the a script.

3.3 Record only on server and share the files via the cloud.

3.1 Export tracks (*.trk) files recorded by DCS World.

3 Is it possible to avoid this problem in the first place?.

Dcs world planes