tNext in not functioning LuaExportActivityNextEvent

[omin]

Prior to the update I was able to export data using  the function LuaExportActivityNextEvent.  I was able to do this both with socket and Io.write. I used the tNext with a time variable, same as your luaexport file. Prior to the update it adhered to the time and data was manageable. Now it ignores tNext and the data balloons to a unmanageable amount especially if using a socket. I am not sure what has changed on your end or if you are doing the export in a different way. Now it behaves like using LuaExportAfterNextFrame function. 

[Flappie]

@omin Can you please attach a track or a mission showing the issue?

[omin]

@Flappie, I appreciate your responds but a track file and mission isn't going to produce what is happening. There are no errors in the log and the mission runs just fine. Matter of fact I even tried this on a mission that runs zero scripts and just has planes flying around. The export is working, it just is not paying any attention to the time variable in order to decrease the amount of data that is sent over the network.

 

There are three functions of when data gets transmitted/or written depending on what you are doing, LuaExportBeforeNextFrame(), LuaExportAfterNextFrame(), and LuaExportActivityNextEvent(t). The t variable is t = LoGetModelTime(). I am using the last function with the variable to create a timer in the for loop using tNext = tNext + 1.0(this is seconds). Prior to the update I would get data sent over the network based on the seconds I provided. I have a feeling that something with function LoGetModelTime() has changed or the data it is attempting to obtain. I could write a script that would  get the LoGetModelTime() return written to the log file in order to see what it produces. 

[Pikey]

Hi Omin,

LuaExportActivityNextEvent

https://wiki.hoggitworld.com/view/DCS_Export_Script

 

I'm not sure the level of support for these export functions but to present this to the Russian developers it will need an example script with the output that is wrong and the last DCS version it worked as expected. The only people that can reliably explain the issue will be whoever is using it and writing exports with it. I'm afraid the current detail sounds OK in words but lacks the example and detail needed for a report to developers, at least, a report that will get noticed.

Please:

functions expected return value
Actual return value
what this affects - 3rd party applications affected
the extent to which this affects these applications (Severity and impact)
Sample script that demonstrates this.

Unfortunately I dont know anyone that has the practical knowledge to properly understand this and report it, welcome to DCS bug reporting