

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?.
